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 - Ed_Arnold

Pages: 1 ... 18 19 20 21 22 [23] 24 25 26 27 28 ... 81
331
z/OS Server / Re: 10.1 Release Notes
« on: September 24, 2019, 10:46:15 AM »
If you're considering implementing CMOD's Encryption at Rest, be sure that you're working from the September 5th, 2019 or later white paper.

It contains an update specifically for z/OS.

IBM Content Manager OnDemand Native Encryption

https://www-01.ibm.com/support/docview.wss?uid=swg27049568&aid=1

And a great companion doc:

Transporting AES encrypted data keys

http://www-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102736

Ed

332
MP Server / Re: LDAP SSL Error after upgrading to 10.1
« on: September 05, 2019, 06:16:24 AM »
teera - thank you for posting your solution.

Ed

333
Report Indexing / ACIF on z/OS - PH01275 is PE
« on: August 29, 2019, 12:19:35 PM »
We found the following in our testing:

https://www-01.ibm.com/support/docview.wss?uid=isg1PH10629&

PH10629: A BUG IN APAR PH01275 CHANGES EXISTING OUTPUT WHEN REPAIRING RECORDS WITH MISSING TRC BYTES WHEN CC AND TRC ARE REQUIRED.

PTFs are available for PH10629.

You can tell what level of ACIF you're on from the APK440I message.

For example:

APK440I  ACIF AT PH01275 HAS COMPLETED NORMALLY WITH RETURN CODE 0.

Ed

334
OD/WEK & JAVA API / Fixpack 10.1.0.5 special consideration
« on: August 21, 2019, 12:51:20 PM »
Included in the ODWEK readme is the following:

https://www-01.ibm.com/support/docview.wss?uid=ibm10958725

Quote
    3.1.10.1.0.5) Release (10.1.0.5)
      - Pre-reqs
        - Previous install of IBM Content Manager OnDemand V10.1
      - Notes:
        - Customer applications that are using the ODWEK Java APIs will need
          to include the Gson jar file, with path, in the CLASSPATH for their
          application. This jar file ships with Content Manager OnDemand and
          can be found in the jars subdirectory of the Content Manager
          OnDemand install location. The file name for Gson version 2.8.1 is
          gson-2.8.1.jar and can be found in the <CMOD install directory>/jars
          directory, where CMOD install directory is your Content Manager
          OnDemand installation directory.

          Examples:
            AIX:
            - CLASSPATH=/opt/IBM/ondemand/V10.1/jars/gson-2.8.1.jar
            Linux:
            - CLASSPATH=/opt/ibm/ondemand/V10.1/jars/gson-2.8.1.jar
            Windows:
            - CLASSPATH=C:\Program Files\IBM\OnDemand\V10.1\jars\gson-2.8.1.jar

335
iSeries / Fixpack 10.1.0.5 special consideration
« on: August 21, 2019, 12:47:39 PM »
ODWEK Java API users need to update CLASSPATH

Beginning with server version 10.1.0.5, customer applications that are using the Content Manager OnDemand Web Enablement Kit (ODWEK) Java APIs will need to include the Gson jar file, with path, in the CLASSPATH for the application.

This jar file ships with Content Manager OnDemand and can be found in the IFS path named /QIBM/ProdData/OnDemand/jars.

For example, the file name for Gson version 2.8.1 is gson-2.8.1.jar.

If this is the name of your most current Gson file, the CLASSPATH statement must be updated to include CLASSPATH=/QIBM/ProdData/OnDemand/jars/gson-2.8.1.jar.

Ed

336
z/OS Server / 10.1.0.5 is now available
« on: August 21, 2019, 12:43:25 PM »
The PTF includes this ACTION HOLD item:

Quote
SPECIAL CONDITIONS:
 ACTION:
   This SYSMOD ships a gson-2.8.1.jar .  After applying
   this SYSMOD, the path to gson-2.8.1.jar must be added
   to all ODWEK java API classpaths.  This includes the
   arsMSVR.sh midserver invocation script.

The sample in /usr/lpp/ars/V10R1M0/samples/arsMSVR.sh has been updated with the following:

Quote
OD_ODAPI=${OD_PATH}/www/api/ODApi.jar:${OD_PATH}/jars/gson-2.8.1.jar
export OD_ODAPI

Ed


337
z/OS Server / Re: JES Extractor
« on: August 14, 2019, 06:06:12 AM »
Just adding that arsjesd is very popular.

Note:  arsjesd comes from the Print Services Facility (PSF) product - is neither developed nor shipped nor supported by the Content Manager OnDemand organization.

arsjesd is the only deliverable that starts with the letters "ars" but doesn't come from CMOD.

Ed

338
Presentations, Newsletters, and such / IBM CMOD Workshops 2019
« on: August 13, 2019, 07:46:49 AM »
Two remaining in Brazil and two remaining in the USA.

https://ibmhybridcloud.lookbookhq.com/cmod-workshops/upcoming-workshops

I plan on being at the workshop in Bethesda - would love to meet the people I only know from here on the ODUG forums!

Ed

339
z/OS Server / High Volume zFS RWSHARE Issue
« on: August 02, 2019, 06:47:34 AM »
CMOD has exposed the following:

OA57775: FILE READ/WRITE FAILURES. OPEN FILE WITH O_APPEND RWSHARE

Opening files with O_APPEND for IO operations can have
unexpected results in an RWSHARE environment sysplex
where concurrent access from multiple systems to the same
file(s) is occurring.

Symptoms vary, depending upon the application but some symptoms
are lseek errors
Ex.
 -EDC5137I Inappropriate I/O control operation
 - Incorrect offsets returned
 - file corruption


This issue was encountered when the CMOD zFS cache was converted to RWSHARE in a very high volume environment.

Ed

340
Report Indexing / Re: Bad Character???
« on: July 30, 2019, 07:28:59 AM »
Dave - I updated my post after your last post.

Just FYI to pick up the (minimal) changes.

Hope this helps!

Ed

341
Report Indexing / Re: Bad Character???
« on: July 30, 2019, 07:15:20 AM »
Hello Dave - I ran into this in 2016 on z. 

Here's some discussion I had on this:

Quote

 With 8.5 comes greater accuracy with handling of non-US characters.
 Typically, this is a symptom of the German "Sharp S" which when
 uppercased becomes two letters.
 
 Here's how you fix it:
 
 a) install PM82660/UK92465
 
 b) add the following to ars.cfg:
     ARS_USE_OLD_STYLE_CASE=1
 
 That's all that's needed to resolve the loading problem.
 
 However,
 
 c) all clients should be at 8.5.0.6 or higher to deal with the
 character being stored as a Sharp S when doing searches.
.....................................................................
 
Related APAR:
 
.....................................................................
 
APAR PM70770 / UK81470 Description
 
 Upper-casing the German s-sharp produces SS.  This expansion of
 the string caused the NULL that  terminated the string to be
 overlaid, causing subsequent string operations to behave
 incorrectly.
 
 PROBLEM CONCLUSION:
 ****************************************************************
 * PROBLEM DESCRIPTION: When running arsload with a applgrp     *
 *                      field that specifies upper-casing and   *
 *                      the field contains a German s-sharp     *
 *                      (U+00DF), the field can either be       *
 *                      truncated, or arsload can abend due to  *
 *                      heap  corruption.                       *
 ****************************************************************
 * RECOMMENDATION:                                              *
 ****************************************************************
 ARNADMP is changed to detect the expansion of the string due to
 the upper-case operation and not overlay the trailing NUL.
 Additionally, ARNADMP will detect if the expansion exceeds the
 size of the field and issue an error message.
 
..................................................................
 
This issue was reported on z and fixed on z.

But then along came the problem on AIX.

For indexing and loading on AIX you also add the following to ars.cfg:
 
     ARS_USE_OLD_STYLE_CASE=1



Just for completeness of this discussion, there was still a problem loading from AIX -> z.

A colleague weighed in with this:

Quote

I have been looking at how to fix this issue and trying to use ars.cfg /
ars.ini on your AIX machine may prove to be a bit tricky.
 
From my tests here on the AIX box you can also specify an environment
variable. Do this for the user(s) who run the arsload command:
 
ARS_USE_OLD_STYLE_CASE=1

The reply was

Quote

...it works!! ...
 
I put
 
export ARS_USE_OLD_STYLE_CASE=1
 
before the call of arsload

Ed

342
MP Server / Re: Why not FileNet for PDF Statements with IBM
« on: July 11, 2019, 11:51:54 AM »
I know zip about FileNet.

You say:

Quote
I'm storing PDF statements only and therefore gaining little-to-no compression savings on storage.

If these are statements do they have repeating images contained therein (what we in CMOD-land call resources) that can be extracted and only one copy of the (for example, fonts and images) gets stored rather than x thousand?

Ed

343
z/OS Server / Fallback
« on: July 11, 2019, 11:27:39 AM »
I've been getting a few questions lately about falling back from V10.1 during an upgrade.

I consulted with the lead architect who had this to say:

Quote
We support a customer trying to upgrade to 10.1, changing the db (e.g arsdb –u) – then if issues, they can fall back to 9.5 [executables - SARSLOAD and HFS] without restoring the database. 

However, always recommended to have db backup

Ed

344
z/OS Server / Recommended OAM service
« on: July 10, 2019, 11:07:38 AM »
OA55720 - HIGH CPU AND UNEXPECTEDLY LONG DURATION OF OSMC PROCESSING FOR 
AN OBJECT STORAGE GROUP   
                                     

ERROR DESCRIPTION:                                             
The customer noticed that when they had an Object Storage Group
with a few hundred thousand objects eligible for transition     
processing and the transition processing resulted in assigning a
management class whose transition criteria set the new pending 
action date (ODPENDDT) to the current date or earlier, that the
processing caused high CPU and took hours to complete. When they
modified their ACS routines to instead assign a new managment   
class whose transition criteria set the new pending action date
to the future, the CPU usage decreased dramatically, as well as
the overall processing time.                                   
                                                               
This issue was incorrectly addressed by FIN APAR OA44651 with   
pending action date behavior changed within base V2R2 release. 
OA44651 pending action behavior was then reverted by APAR       
OA55718. Please see OA44651 and OA55718 for additional details.
                                                               
Additional Keywords: OSMC CPU OAM OBJECT                       
                                                               
LOCAL FIX:                                                     
Ensure that the management class being assigned during         
transition processing sets the pending action date to a future 
date, via either the transition criteria or the expiration     
date in that management class.                                 



OA57287 - OSMC PROCESSING SLOWDOWN FOR STORAGE GROUPS WITH LARGE AMOUNT   
OF OBJECTS (APPRX. HALF A BILLION) AFTER OA55720. 
             

ERROR DESCRIPTION:                                               
After the application of APAR OA55720, OSMC processing slows     
down when a particular storage group has a large number of       
objects. Objects are processed successfully, but the processing 
takes significantly longer. The customer noticed the difference 
in processing time was significant for storage groups that had   
approximately half a billion objects.                           
                                                                 
LOCAL FIX:                                                       
Do not start OSMC processing for storage groups with a large     
amount of objects.                                               


345
Had a couple reports come in almost at the same time of an ARSXML export error.

This is on V9.5. 

Note:  On V9.5 ARSXML is exploiting 64 bit. There are a few functions in V9.5 that are already 64 bit and ARSXML is one of them.

The error message seen was:

ARS7764I Export of applicationGroup, INVOICES1 failed.                   
File=//'SYS17205.T110034.RA000.ARGAPPLG.SRCCMS.H01(ARGAPPLG)', Line=3669


No other error messages.

One would think that it's running out of space trying to create a temporary file out on disk somewhere.

Not so.  The ARSXML export is trying to allocate space above the 2 gigabyte bar.

The problem was the IEFUSI exit in both cases.

Specifying REGION=0M wasn't giving sufficient storage above the bar.

The circumvention (rather than fix the IEFUSI exit) was to specify MEMLIMIT=10G on the JOB card.

Ed

Pages: 1 ... 18 19 20 21 22 [23] 24 25 26 27 28 ... 81