Messages

571

z/OS Server / Not running ARSSYSCR system log update can cause issues for ARSRPT

« on: October 11, 2017, 08:01:00 AM »

In the CMOD V8.4.1 (yes, V8.4.1) readme was an optional step to run arssyscr.

This switched the CMOD system log to using the new date/time format (much more granular).

It also increased the size of the MSG_TEXT field to 2,000 chars.

Now, years later, we're running into S0C4's in ARSRPT from shops who haven't updated their system log yet.

This is due to a truncated file from an ARSDOC QUERY which ARSRPT uses behind the scenes, because of the smaller MSG_TEXT field.

Ed

572

z/OS Server / OAM OA51129 is PE'd

« on: October 10, 2017, 10:52:17 AM »

This maintenance has been PE'd by two other pieces of maintenance.                         
.                                                                         
**** PE17/05/10 FIX IN ERROR. SEE APAR OA52831  FOR DESCRIPTION           
.                                                                         
**** PE17/08/04 FIX IN ERROR. SEE APAR OA53620  FOR DESCRIPTION         

Ed

573

Report Indexing / Second of two PDF's

« on: October 10, 2017, 08:58:58 AM »

The rest of the story...   

Ed

574

Report Indexing / XML Indexing - Bud Paton's PDF's from the Toronto 2016 CMOD Road Show

« on: October 10, 2017, 08:57:28 AM »

Attached with Bud's permission - thanks guy!

Ed

575

Report Indexing / Re: XML Indexing - Getting Started With A Proof of Concept

« on: October 10, 2017, 08:48:34 AM »

This part I have not tried yet.  Will try to do this when I get some spare time:


The user has to write the transform to take their XML and put it into a format ready for the OD XML indexer. They then need to run a transform engine to create the input file. One possibility is to use Saxon [google it, available on the net] so the command is:

java -classpath d:\saxon\saxon9he.jar net.sf.saxon.Transform -s:cd_catalog.xml -xsl:cd_catalog.xslt -o:cd_catalog.in

This will process the users XML data into an OD XML indexer input file.

Then to make the resources ingested to OD the best way is to zip them up. To do that run the following command:

zip cd_catalog.in.res cd_catalog.css

This added the css file to the res file for the load. Note: All resources for XML AG's are just zip files and they have to be named the same as the input file with the '.res' extension.

At this point it's the same load command as used previously:

arsload -g <group> -h <hostname> -u <user> -p <password> -nvf xxxxxxx.in

This will load the file and you should see a message about  the resources being loaded. After loading you can view on of the documents loaded in either the windows client or through ICN. In both scenarios the resources (zip) file will be retrieved and unzipped so that when the browser views the data it will apply the CSS to style the content.

Ed

576

Report Indexing / Notes for z/OS

« on: October 10, 2017, 08:10:15 AM »

To edit cd_catalog.in here's what I did:

1. rename it to cd_catalog.original.cs

2. iconv -f UTF-8 -t IBM-1047 cd_catalog.original.cs > cd_catalog.ebcdic.cs

3. oedit cd_catalog.ebcdic.cs, save

4. iconv -f IBM-1047 -t UTF-8 cd_catalog.ebcdic.cs > cd_catalog.cs

577

Report Indexing / Re: XML Indexing - Getting Started With A Proof of Concept

« on: October 10, 2017, 08:02:54 AM »

First thing we will do is verify that we can load our sample XML files.


To do that we need to point the file cd_catalog.in to odxmlidx.xsd so that it can find the declaration for element 'odidx'

On my system odxmlidx.xsd is noNamespaceSchemaLocation="/u/odv733/xml/xmlload/odxmlidx.xsd"

On Windows the location is noNamespaceSchemaLocation="c:\progra~1\ibm\ondemand\v10.1\xml\odxmlidx.xsd"

Save, of course.


At this point you can verify that arsload will correctly load the data with the following command:

arsload -g ELA-XML -h <hostname> -u <user> -p <password> -nvf cd_catalog.in


You should also be able to view this with the user client.

578

Report Indexing / Re: XML Indexing - Getting Started With A Proof of Concept

« on: October 10, 2017, 07:45:07 AM »

cd_catalog.css - this is the style sheet provided by the customer

cd_catalog.xml - this is the customer's source file, contains several records/elements they want archived

cd_catalog.xslt - this is the customer's file they wrote to put cd_catalog.xml into the ondemand XML indexer format

cd_catalog.in   - this is the OD XML indexer input file. see below for how this is produced

cd_catalog.in.res - this is the zipped resource (in this case cd_catalog.css)

579

Report Indexing / Re: XML Indexing - Getting Started With A Proof of Concept

« on: October 10, 2017, 07:39:41 AM »

These next files are input to arsload and need to have the low level qualifier of "txt" removed.  I had to add "txt" so that they could be uploaded.

580

Report Indexing / XML Indexing - Getting Started With A Proof of Concept

« on: October 10, 2017, 07:36:58 AM »

Text summaries of the APPL, AG, and FOLDER:

581

z/OS Server / OAM OA51129 Causes Problems for V2 Migrated Data - Resolved

« on: October 09, 2017, 07:18:05 AM »

Ref:  Hans' thread:   http://www.odusergroup.org/forums/index.php?topic=2327.0

With OA51129, OAM now goes into a path where it needs what's in package in CBRHTBSV.*

When ARSZDOCG was created to retrieve the V2 data, it had to have the OAM packages bound to it.  Back then,  CBRHTBSV.*   wasn't used or didn't exist, so it wasn't included in SARSINST(ARSLDOCG).

Solution:   APPLY CMOD PI86710

PROBLEM SUMMARY:                                                 
****************************************************************
* USERS AFFECTED: ALL CONTENT MANAGER ONDEMAND FOR Z/OS 9.0    *
*                 AND ABOVE CUSTOMERS USING INDEX              *
*                 MIGRATION PROGRAM AND DOCUMENT RETRIEVAL     *
*                 PROGRAM.                                     *
****************************************************************
* PROBLEM DESCRIPTION: V2/IAFC OAM ERROR: ARSZDOCG:            *
*                      00000017(00000010) RETURN CODE=         *
*                      0000000C           REASON-CODE=         *
*                      9404FCDB ERROR OCCURS WHEN CBRKCMF.*    *
*                      AND CBRHTBSV.* ARE NOT IN PKLIST FOR    *
*                      ARSLDOCG                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
ADDED CBRKCMF.* AND CBRHTBSV.* TO PKLIST IN ARSLDOCG.SAMP.       
                                                                 
PROBLEM CONCLUSION:                                             
ADDED CBRKCMF.* AND CBRHTBSV.* TO PKLIST IN ARSLDOCG.SAMP TO     
ELIMINATE V2/IAFC  OAM ERROR: ARSZDOCG: 00000017(00000010)       
RETURN CODE= 0000000C REASON-CODE= 9404FCDB ERROR.  CBRKCMF     
AND CBRHTBSV HAVE BEEN AVAILABLE SINCE Z/OS 1.10 AND ABOVE.     

APPLICABLE COMPONENT LEVEL/SU:
RA10 PSY UI50856 UP17/10/05 I 
R900 PSY UI50857 UP17/10/05 I 
R950 PSY UI50858 UP17/10/05 I 

582

z/OS Server / Re: ARS0020E OAM ERROR: FUNCTION=QUERY RETURN CODE=0000000C REASON-CODE= 9404FCD4

« on: October 03, 2017, 09:37:37 AM »

Is there a straightforward answer to that?

I don't have an answer.

All I know is that OAM APAR OA51129 is unearthing some issues.

Expect to see more on this in the next couple weeks.

Ed

583

z/OS Server / Re: ARS0020E OAM ERROR: FUNCTION=QUERY RETURN CODE=0000000C REASON-CODE= 9404FCD4

« on: September 28, 2017, 07:36:09 AM »

Hello Hans - I think you might be getting bit by this one:

"After applying z/OS maintenance I can no longer retrieve OnDemand V2 migrated documents."

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

Ed

584

z/OS Server / Re: CMOD load abends 0C4

« on: September 28, 2017, 07:33:29 AM »

As this is a new APAR, I'll assume that you have this already installed?

OA51129 - New Function - Co-existence (enablement) for future support

R210   UA91366   
R220   UA91367

Ed 

585

OD/WEK & JAVA API / HTML5 Viewer Now Available, Ships With CMOD V10.1.0.1

« on: September 26, 2017, 07:57:49 AM »

Documentation for the HTML5 viewer:

http://www.ibm.com/support/docview.wss?uid=swg22008705

CMOD V10.1.0.1 Fixpack readme:

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

Ed