Messages

31

MP Server / Issue Loading to S3 (EMC)

« on: October 27, 2023, 09:29:47 AM »

Hi all,

Working on loading to EMC via S3.

Within ars.s3 - We have defined-

Code: [Select]

ARS_S3_VENDOR=EMC
ARS_S3_REGION=...
ARS_S3_SERVER=...
ARS_S3_SERVICE=S3

The message after trying to load -

Code: [Select]

S3 Interface (AMAZON) Error: Message=Couldn't resolve host name, Resturn Code=6
One thing to note, we can ping the S3_SERVER from our desktops, but not from the server we are trying to load from.

Not sure if this is an S3 configuration issue or a CMOD config issue. The one thing that is wondering me is since its trying to resolve AMAZON, yet EMC is defined as the provider..?

32

MP Server / Re: OnDemand on Linux fails with Higher Version (CMOD 9.5)

« on: September 26, 2023, 02:36:46 PM »

Just a quick note to thank Roberto and Alessandro for this thread...  Almost 10 years later, it helped me upgrade a client from v7 all the way to v10.5...

Another awesome display of the power of the forums. 

-JD.

10.5.0.7?

We're having what appears to be install anywhere / java issues with RHEL on that one.

Code: [Select]

[root@server od]# ./odlinux1057.bin -i console -DOD_HIGHER_VERSION_CHECK=false
Preparing to install
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Error: Could not find or load main class com.zerog.lax.LAX
Caused by: java.lang.ClassNotFoundException: com.zerog.lax.LAX
Google related to another product said to try this:

Code: [Select]

export JAVA_TOOL_OPTIONS=-Djdk.util.zip.disableZip64ExtraFieldValidation=true
So doing this along side

Code: [Select]

./odlinux1057.bin -i console -DOD_HIGHER_VERSION_CHECK=false
Prompted me to:

Code: [Select]

Please Wait
-----------
------|-------
    1- Yes to All
    2- Yes
    3- No
    4- No to All

A newer file named "commons-text-1.10.0.jar" already exists at
   "/opt/ibm/ondemand/V10.5/jars".
Which led to:

Code: [Select]

Installation Complete
---------------------

Congratulations. IBM OnDemand V10.5 has been successfully installed to:

   /opt/ibm/ondemand/V10.5

PRESS <ENTER> TO EXIT THE INSTALLER:
[root@server od]# /opt/ibm/ondemand/V10.5/bin/arsxml
ARS7700I Usage: arsxml add|update|delete|export|validate [options]
        Version:  10.5.0.7

33

z/OS Server / Re: DSNT408I SQLCODE = -804, ERROR

« on: August 17, 2023, 07:36:50 AM »

Here's some total WAGs:

Check app group definitions to make sure AcctNo has the same definition in all App Groups

If you have database access, something like:

Code: [Select]

select * from arsagfld where name like 'acctNo' will make any differences a little more obvious.

Turn off parameter markers for queries

Ask your DBA to check their diagnostic logs (db2diag.log in the LUW world) for more info.

-JD.

Turning off parameter markers gave us the results I need -> I think. We're able to see the queries and are still investigating.

I've never had to touch that checkbox before. Thanks from myself and my colleagues.

34

z/OS Server / DSNT408I SQLCODE = -804, ERROR

« on: August 15, 2023, 09:46:22 AM »

Hello all,

CMOD 10.5.0.6
Z/OS 4.28.0
DB2 12.01.0005

We are working with IBM on a case related to this. I am wondering if anyone has seen something such as this.

We have a folder that has 6 application groups - One of the application groups has around 160 tables associated with it.

There's a field named "AcctNo"

Via the client - when we run "Account Number" in then in the search box for example 11111 22222 33333 44444 55555, we get the following:

The same happens when I try via arsdoc get or query.

Code: [Select]

DB Error: {DB2 FOR OS/390}{ODBC DRIVER}{DSN12015}   DSNT408I SQLCODE = -804, ERROR:  AN ERROR WAS FOUND IN THE APPLICATION PROGRAM            INPUT PARAMETERS FOR THE SQL STATEMENT, REASON 07                       DSNT418I SQLSTATE   = 07002 SQLSTATE RETURN CODE                                 DSNT415I SQLERRP    = DSNXECP SQL PROCEDURE DETECTING ERROR                      DSNT416I SQLERRD    = -202  0  0  -1  262124  0 SQL DIAGNOSTIC INFORMATION       DSNT416I SQLERRD    = X'FFFFFF36'  X'00000000'  X'00000000'  X'FFFFFFFF'                  X'0003FFEC'  X'00000000' SQL DIAGNOSTIC INFORMATION                      ERRLOC=5:10:2 -- SQLSTATE=07002, SQLCODE=-804, File=arsdoc.c, Line=3526


35

Report Indexing / Re: Issues with PPDs + Resources

« on: August 09, 2023, 11:19:26 AM »

Thanks JD - Thats actually on my list - But I have not tried that today as I am putting out fires with a water gun.

All versions up to date 10.5.0.6 ZOS Lib, 10.5.0.6 Linux Loader

36

Report Indexing / Issues with PPDs + Resources

« on: August 08, 2023, 03:35:23 PM »

We are seeing an issue with PDFs with our last month-end run. PDF files are now being returned with the full resource block for the entire file. About 35 MB worth, even though the PDF itself is only around 170KB. There is also now a fear of NPI data breach.

Example - Customer XYZ is picking up a resource that should only be shown to customer ABC.

We're using PPD's for this:

INDEXSTARTBY=1
RESTYPE=ALL
INDEXMODE=INTERNAL
REMOVERES=YES
BOOKMARKS=NO

Has anyone seen this before.. or does anyone have any suggestions?

Thanks

37

Windows Client / Re: Efficient retrieval of a large number of large documents

« on: August 07, 2023, 09:18:41 AM »

i have no experience writing powershell scripts, but if i was to do this in bash:

I'd get a listing of the DOC_NAME's from the system log or the data table.. Then do-

arsdoc get -u user -p password -agcNv -G "App group" -i "where DOC_NAME='FAA2'" -o docname -h cmodhost

or you can do something like-

arsdoc get -u user -p password -agcNv -G "App group" -i "where ACCTNO='12345'" -o docname -h cmodhost

first option is more efficient, get the complete docs via the DOC_NAME.
second option will take alot of time, but it will work if you have a listing of metadata to retrieve.

38

z/OS Server / ARSMAINT - Catchup after migration

« on: July 11, 2023, 12:55:03 PM »

Hi All,

we are planning on running arsmaint after not running it for a few months - due to moving to a new Z/OS platform.

Is there any way to "Simulate" a document count of what would be expired..if that makes sense.

We plan on just using arsmaint -d -g <app group>

We'd like to know how much we have to get caught up on.

Thanks!

39

z/OS Server / Is it possible to run arstblsp remotely against ZOS?

« on: April 18, 2023, 07:11:34 AM »

Our use case is that us CMOD Devs occasionally will need to view open tables, close tables - etc. And currently we need to engage our Z/OS DB2 folks.

I have my library server running on Z/OS, and a utility server that has CMOD, the database cataloged, etc.

I can connect to the database with an instance that was setup on the box, no issue - view all the tables, etc.

db2 connect to CMODDEV user <guestpass> using <password>

Within ARS.ini- I defined the INSTANCE as CMODDEV and the instance owner as archive (the local instance on the box)

I added the Z/OS DB2 guestpass/userid to the stash file - and within ars.ini - I am pointing to that stash file.

I switch to the archive user and here's what I get (Just trying to view now, for a POC..)

Code: [Select]

[archive@server ~]$ arstblsp -a 3 -g APPGROUP -h CMODDEV
ARS0013E DB Error: [IBM][CLI Driver][DB2] SQL0204N  "SYSIBMADM.DBCFG" is an undefined name.  SQLSTATE=42704  -- SQLSTATE=42S02, SQLCODE=-204, File=arssys.c, Line=332
ARS1107E An error occurred.  Contact your system administrator and/or consult the System Log.  File=arstblsp.c, Line=1929

40

Report Indexing / Re: Ignore 2GB File Limit with Daemon

« on: April 12, 2023, 11:34:02 AM »

There doesn't seem to be any documentation on this option -- do you have any info you can share on this option?

-JD.

Zilch!

I added it to the profile. Will add any findings.

41

Report Indexing / Re: Ignore 2GB File Limit with Daemon

« on: April 11, 2023, 08:22:38 AM »

Exporting it in the profile of the account that runs the process (or in the shell script that starts the arsload daemon) is the right way forward.

-JD.

Thats what I thought - But I was not sure if it was one of those things you'd include in ars.cfg also! Thanks!

42

Report Indexing / Ignore 2GB File Limit with Daemon

« on: April 10, 2023, 11:50:33 AM »

Hi All,

Just wondering if anyone is using:

Code: [Select]

ARS_LOAD_IGN_2GB_DOCUMENT_LIMIT_ERROR=1
With a load daemon - Or if this is something that we can specify in ars.cfg? We currently have to manually execute it every time we go to load a certain subset of files.

Would an

Code: [Select]

export ARS_LOAD_IGN_2GB_DOCUMENT_LIMIT_ERROR=1 in the profile that runs our load Daemon also work?

Thanks!

43

Report Indexing / Re: Failure with special character

« on: March 08, 2023, 11:05:04 AM »

Thanks, wasnt sure if it was the same on the mainframe side

44

Report Indexing / Re: Failure with special character

« on: March 03, 2023, 12:59:41 PM »

If you have a test environment, you might experiment with the ARS_USE_OLD_STYLE_CASE parameter in the ARS.CFG file.

Use the following if upper casing expands the number of characters, for example the German Ezett (ß) expands to SS with the new style (ICU) upper casing
In the ARS.CFG:
# Use old style upper casing to prevent character expansion
#
ARS_USE_OLD_STYLE_CASE=1

When value of ARS_USE_OLD_STYLE_CASE is:

(0) - then we do all upper/lower casing in UTF-16 (no change)
(1) - then we do all upper/lower casing in OS level codepage we are running under (no change)
this was really added just to prevent the german sharp s (ß) character not expand to multiple bytes (which it does in UTF-8)
(2) - we now upper/lower case in UTF-16 (however we specifically prevent ß from being done).
We then convert this back to the native codepage (of the data) - then compare to the original string that was provided to us.
If we find any characters that are not found (e.g. ICU will change the char to be a substitution char),
we will put the original char back into the upper/lower case string. If for any reason this fails we will
default as if the ARS_USE_OLD_STYLE_CASE=1 for that string.

Yup- I saw that as well. Do you know if that requires a recycle of ARSSOCKD? I only ask because we are on Z/OS and we'd have to do some coordination.

45

Report Indexing / Failure with special character

« on: March 02, 2023, 06:25:01 PM »

We have an issue when loading a name field.

 ARS1127E Row 1:  The string "JUAN CARLOSÑORTEGA                                               " has a length of 83 and the field has a maximum length of 80

The special character added by what I am assuming the "Ã" is causing the field to spill into 83 characters. I've tried removing space, removing tab, etc.

the only fix that I was able to get working in a "timely" matter - is recreate the AG, and for the field info:

String: Case(Mixed)
Type: Variable

IBM suggested that - But I am wondering if anyone knows of a way to do it at the application level so I don't have to recreate an application group.