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.


Topics - Ed_Arnold

Pages: 1 2 3 4 [5] 6 7 8 9 10 ... 14
61
z/OS Server / Program Directories for 9.5, 10.1
« on: November 27, 2017, 09:49:50 AM »
Getting ready to upgrade to a supported release?

V9.5 and V10.1 program directories are available here:

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

Ed

62
z/OS Server / ACIF V4.3.0 went EoS 6/30/2017
« on: November 15, 2017, 10:19:01 AM »
This slipped past me.

Everyone should be on V4.5.0.

Ed

63
Report Indexing / ACIF V4.3.0 went EoS 6/30/2017
« on: November 15, 2017, 10:18:13 AM »
This one slipped right past me.

All shops should be on V4.5.0.

Ed

64
Bottom line is that z/OS V2R3 OAM changes how OAM keeps track of things.  If OAM's internal information was manipulated (changed via an SQL UPDATE command for example) outside of OAM commands, z/OS V2R3 can expose errors that previously remained hidden.

II14842: INSTRUCTIONS AND TOOL AVAILABLE FOR OAM OBJECT USERS TO HELP DIAGNOSE OUT-OF-SYNC COLLECTION ENTRIES BETWEEN CATALOG AND DB2.

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

Ed

65
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


66
Attached with Bud's permission - thanks guy!

Ed

67
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:




68
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 




70
z/OS Server / z/OS V2.1 - the base operating system - EoS 30 September 2018
« on: September 13, 2017, 10:36:33 AM »
https://www-01.ibm.com/software/support/lifecycleapp/PLCDetail.wss?q45=Z966844T77753Y85

Just FYI to all that hopefully your shop has plans to migrate in the next 12 months to z/OS V2.2 if it hasn't already.

Ed

71
z/OS Server / Running ARSMAINT via SSL to ARSSOCKD - Proof of concept
« on: August 31, 2017, 09:49:57 AM »
Can we have ARSMAINT connect to ARSSOCKD via SSL?

I already had a keyring and certificate created as per the other SSL on z/OS related post:

http://www.odusergroup.org/forums/index.php?topic=1938.0

Note that the userid associated with the keyring is the same as the userid of the started task, in my case ARSSV950.

I have the following SSL parms in my ars.ini:

Quote
SSL_PORT=11449                     
SSL_KEYRING_FILE=ARSSOC95.SSLRING 
SSL_KEYRING_LABEL=ARSSOC95.CERT   
SSL_CLNT_USE_SSL=1                 

I ran the following batch job which updates statistics on the DB2     
database.  Be sure you do this on a test system if you use the -r parm!
                                                                     
Quote
//TMP1  EXEC  PGM=IKJEFT01,                                           
//            DYNAMNBR=200                                           
//SYSPROC  DD  DSN=SYS1.SBPXEXEC,DISP=SHR                             
//*                                                                   
//SYSTSPRT DD  SYSOUT=*                                               
//*                                                                   
//SYSTSIN  DD  *                                                     
 oshell logger -d1 starting ARSMAINT run                             
 oshell /usr/lpp/ars/V9R5M0/bin/arsmaint -I ARCH950 -r               
 oshell logger -d1   ending ARSMAINT run                             
//*                                                                   
//STDENV  DD *                                                       
_BPX_SHAREAS=YES                                                     
_BPX_BATCH_SPAWN=YES                                                 
/*                                                                   
//OSHOUT1 DD SYSOUT=*,DCB=(RECFM=F,LRECL=255)                         
//STDOUT DD SYSOUT=*                                                 
//STDERR DD SYSOUT=* 
 
                                             

The first time I ran it I had REGION=7M on the job card and received:
Quote
ARS0000E Initialization of ICU for directory >/usr/lpp/ars/V9R5M0/locale/< failed - please ensure proper installation

I changed the JOB card to REGION=0M and this time I got the following on the z/OS console:

Quote
IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00036                 
ICH408I USER(ODADMIN ) GROUP(ODCMARS ) NAME(EDWARD ARNOLD       )
  IRR.DIGTCERT.LISTRING CL(FACILITY)                             
  INSUFFICIENT ACCESS AUTHORITY                                 
  ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   ) 

A quick trip to the google says I should run the following:

Quote
rdefine facility irr.digtcert.listring uacc (none)

permit irr.digtcert.listring class(facility) id(*)       acc(read)

SETROPTS RACLIST(facility)  REFRESH


Try again, still won't connect.

I received a suggestion to add a USER=ARSSV950 to the JOB card.

Eureka!  It works.

If you're trying to see if you can use ARSMAINT via SSL, these instructions should be a good IVP.

Ed



72
z/OS Server / z/OS 2.3 - OAM Line Item of Interest for CMOD
« on: July 20, 2017, 07:43:02 AM »
IBM z/OS Version 2.3 Announcement Letter:

https://www.ibm.com/common/ssi/rep_ca/9/872/ENUSAP17-0239/ENUSAP17-0239.PDF

Quote
In z/OS V2.3, an optional multiple OAM configuration enables a separate OAM tape library address space and up to two OAM object support address spaces...

What this means is that one could have TEST and PROD CMOD instances using separate TEST and PROD OAMs on the same LPAR or two independent CMODs and OAMs on the same LPAR.

Ed

73
z/OS Server / 10.1 Release Notes
« on: May 25, 2017, 09:53:05 AM »
CMOD V10.1 is compiled with option ARCH( 8 ), meaning a z10 processor or newer is required.

Running on any processor prior to a z10 is likely to result in a S0C1.

Note:  z/OS 2.2 pre-reqs a z10 processor.

Also, CMOD V10.1 is compiled with the option TARGET(zOSV2R2).

Bottom line:  don't try to run CMOD V10.1 on z/OS 2.1.

Ed

74
The windows admin client, if 64 bit, then sample data for PDF indexer does not work.... must use 32 bit client.

https://www.ibm.com/support/knowledgecenter/SSQHWE_10.1.0/com.ibm.ondemand.ir.doc/dodig087.htm

Ed

75
ICN documentation was incorrect in saying that ICN 3.0 is not supported on CMOD 10.1.

1. PMRs that come in for ICN V3.0 configured against CMOD V10.1 will be fully addressed. 
2. ICN support is updating the clearing house prerequisite documentation and the updated documents  will show the changes by 5/26/17.
3. CMOD V10.1 already packages ICN V3.0 on Passport Advantage.  ICN V3.0 can also be downloaded from Fix Central.

Ed

Pages: 1 2 3 4 [5] 6 7 8 9 10 ... 14