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

Pages: [1] 2 3 4 5
1
z/OS Server / Re: 10.1 Release Notes
« on: June 16, 2021, 01:15:12 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
Is this still the case. We have other problems with 10.1, OAM issues, but not S0C1.
Release                  z/OS 2.1.0 (SPLevel 7.2.1)   

2
Thanks Ed

I got Covid19 and back again just now.
I will go on with the suggestions you made.

/ib

3
Will it be safe to run the upgrade sequence once again?

4
The error is not permission :

ARS4034I Creating index ZSTARSS.arsag_name_idx                                   
ARS4054E DB Error: æDB2 FOR OS/390åæODBC DRIVERåæDSN12015å                       
 DSNT408I SQLCODE = -601, ERROR:  THE NAME (VERSION OR VOLUME SERIAL NUMBER) OF 
          THE OBJECT TO BE DEFINED OR THE TARGET OF A RENAME STATEMENT IS       
          IDENTICAL TO THE EXISTING NAME (VERSION OR VOLUME SERIAL NUMBER)       
          ZSTARSS.ARSAG_NAME_IDX OF THE OBJECT TYPE INDEX                       
 DSNT418I SQLSTATE   = 42710 SQLSTATE RETURN CODE                               
 DSNT415I SQLERRP    = DSNXISB1 SQL PROCEDURE DETECTING ERROR                   
 DSNT416I SQLERRD    = 120  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION           
 DSNT416I SQLERRD    = X'00000078'  X'00000000'  X'00000000'  X'FFFFFFFF'       
          X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION                   
  ERRLOC=5:10:1 -- SQLSTATE=42S11, SQLCODE=-601                                 
ARS4035E Unable to create index ZSTARSS.arsag_name_idx                           

And a closer look in the output also shows this:

ARS4054E DB Error: æDB2 FOR OS/390åæODBC DRIVERåæDSN12015å               
 DSNT408I SQLCODE = -205, ERROR:  DOC_UUID IS NOT A COLUMN OF TABLE       
          ZSTARSS.ARSHOLDMAP                                             
 DSNT418I SQLSTATE   = 42703 SQLSTATE RETURN CODE                         
 DSNT415I SQLERRP    = DSNXIIKY SQL PROCEDURE DETECTING ERROR             
 DSNT416I SQLERRD    = 30  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION     
 DSNT416I SQLERRD    = X'0000001E'  X'00000000'  X'00000000'  X'FFFFFFFF'
          X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION             
  ERRLOC=5:10:1 -- SQLSTATE=42S22, SQLCODE=-205                           
ARS4035E Unable to create index ZSTARSS.arsholdmap_idx                    

5
z/OS Server / Columns missing in ARSSYS after upgrade to 10.1 from 9.5
« on: April 29, 2020, 03:56:38 AM »
How do I fix this?

Problem with table: ARSSYS after upgrade to V10.1.
It seems that 5 Columns are missing in table : ARSSYS
 
When Starting ARSSOCKD Ondemand ends and says:

---- WEDNESDAY, 29 APR 2020 ----                                             
 IEF403I ARSSOCKD - STARTED - TIME=12.41.38                                 
 ARS0013E ARSSOCKD DB Error: æDB2 FOR OS/390åæODBC DRIVERåæDSN12015å
 DSNT408I SQLCODE = -206, ERROR:  KEYSTORE_TYPE IS NOT VALID IN THE         
 CONTEXT                WHERE IT IS USED                                     
                        DSNT418I SQLSTATE   = 42703 SQLSTATE RETURN CODE     
                                 DSNT415I SQLERRP    = DSNXORSO SQL         
 PROCEDURE DETECTING ERROR                     DSNT416I SQLERRD    = -       
 100  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION            DSNT416I         
 SQLERRD    = X'FFFFFF9C'  X'00000000'  X'00000000'  X'FFFFFFFF'             
          X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION               
           ERRLOC=5:10:1 -- SQLSTATE=42S22, SQLCODE=-206, File=arssys.c, Line=3827                                                                   
 ARS0151E ARSMSG Unable to initialize server database system parameters.  Contact your system administrator.                         
               
-
I located the SQL in DB2 log: 
SELECT  keystore_type , keystore_location , keystore_mkl ,   
               keystore_mkl_dt , data_ekey 
                           FROM ZSTARSS.ARSSYS FETCH FIRST 1 ROW ONLY 
                         OPTIMIZE FOR 1 ROW FOR FETCH ONLY


All listed columns are missing in ARSSYS table. And ARSSYS has not been updated since 2016.
Before that I ran  the update steps. With nothing related to missing the colums :

/usr/lpp/ars/V10R1M0/bin/arsdb -I ARCHIVE -vu

These comes 9 times:
ARS4121I Altering table ARSSYS                 
[/i]ARS4123I Table ARSSYS has already been updated
And no errors

/usr/lpp/ars/V10R1M0/bin/arsdb -I ARCHIVE -vr      
Only this error is displayed:
ARS4035E Unable to create index ZSTARSS.arsag_name_idx                         

/usr/lpp/ars/V10R1M0/bin/arsdb -I ARCHIVE -vfe       ;
Table arssys is not deleted

/usr/lpp/ars/V10R1M0/bin/arsdb -I ARCHIVE -mv
Updating runstat statistics for table ZSTARSS.arssys   
And no errors
                       

6
z/OS Server / Re: ARS1109E Unable to allocate enough memory
« on: June 04, 2019, 01:08:02 AM »
Hi
/tmp is zFS.
and 306  "Object size 306" is, yes, Object size 306.

I think we wait for solution from PMR.

But thanks for the interrest anyway.
/ Marthin

7
z/OS Server / Re: ARS1109E Unable to allocate enough memory
« on: June 03, 2019, 03:32:14 AM »
After changed REGION to 0M we still face the problem.
So for now both the ARSSOCKD task and the ARSLOAD step has REGION=0.

8
z/OS Server / Re: ARS1109E Unable to allocate enough memory
« on: May 30, 2019, 07:33:01 AM »
Hi

REGION=512M

Embarrassing I did'nt check that first.
I will change this to REGION=0M ASAP

Thanks Greg  :)

9
z/OS Server / ARS1109E Unable to allocate enough memory
« on: May 30, 2019, 05:36:50 AM »
Hi out there

We face this problem more often - and have a PMR open for it.
But I just want to hear if anyone have seen it for OnDemand 9.5.0.6.
I can't figure what kind of "Memory" that is short. The /tmp is not the problem. The ARSLOAD is running with REGION=0K

2019-05-30 00:29:17.305779: ARS1109E Unable to allocate enough memory. File=SYS16180.T182004.RA000.ARNLOAD.SRCCMS.H01(A     
RNLOAD), Line=6311
2019-05-30 00:29:17.307399: ARS1157E Unable to store the object >3918<.  Object size 306
2019-05-30 00:29:17.307413: ARS4311E Loading failed                                                                           
2019-05-30 00:29:17.307969: ARS4318E Processing failed for file >/usr/lpp/ars1/DB2N/tmp//16777874.0000016B06256813

(DD:INPUT-SYS19150.T022836.RA000.PFLSD888.DCFOD.H01)<
ARS1109E Unable to allocate enough memory.  File=SYS16180.T182004.RA000.ARNLOAD.SRCCMS.H01(ARNLOAD), Line=15163               
ARS4323E Unable to log load information
2019-05-30 00:29:17.324308: ARS4327E Processing has stopped.  The remaining files will NOT be processed. 

And today we even get memory shortage on READ:

30-05-2019 12:16:27   ODREADX1       2041440   Error   No       24   Object >13115< in Application Group >FAA< not found in node >DB2G.VEAVTALE.ODSG155.MCOBJ155 <  Srvr->server.name 10.181.23.1 non-SSL<-
30-05-2019 12:16:27   ODREADX1       2041440   Error   No      430   OAM Error: ARSSMMVS line 1188: 00000015 13451599 bytes (EDC5132I Not enough memory. (errno2=0x00000000)), Return Code=21, Reason=0, File=arssmsms.cpp, Line=1893  Srvr->tServer_name 10.181.23.1 non-SSL<-

I I xheck ulimit, it looks ok to me:
Å ulimit -a                   
core file         unlimited   
cpu time          3602         
data size         unlimited   
file size         unlimited   
stack size        unlimited   
file descriptors  65535       
address space     75240k       
memory above bar  2048m       

/regards
Marthin

10
z/OS Server / Re: Too many tables in Appl. group
« on: October 10, 2018, 12:53:28 AM »
The IBM Lab suggested to use this in ars.cfg:
ARS_DB_MAX_SQL_TABLES=250
This is for now the solution . After this - and making a new much larger table - we don't get errors on searches caused by the large SQL statement.

11
z/OS Server / Re: Too many tables in Appl. group
« on: September 26, 2018, 05:58:34 AM »
Thank you both.
While fixing the problem, the use of the Segment field seems work now

12
z/OS Server / Too many tables in Appl. group
« on: September 26, 2018, 02:15:27 AM »
Hi

We suddenly ran into a problem with too many tables for one of the Appl. Groups. After table number 260 the SELECT statements became too long.

So question is: Has anyone expierenced this?
Also: can I concatenate all the 260 tables into one larger table BAA261 - close the table BAA260 and create an new Application group with a larger row number - and then modify the ARSSEG table to use only the new tables -and how.?

Or is there a better way to do this to avoid modifing ARSSEG?

13
z/OS Server / Re: Ready for DB2 v12
« on: January 03, 2018, 02:21:32 AM »
Thank you both  :)

14
z/OS Server / Ready for DB2 v12
« on: December 21, 2017, 11:44:57 PM »
Hello out there

Planning to upgrade DB2 to v12, I am asked if OnDemand 8.5 and 9.5 have any issues.
I traveled across the Internet and could only find info referring to DB2 V11.1
Does anyone have plans with DB2 v12?

15
z/OS Server / Re: OnDemand z/OS V9 compatibility with z/OS 2.3
« on: November 24, 2017, 05:30:08 AM »
Hi Ed

I see you are already involved.
The PMR is already made.

/ Ib Marthin

Pages: [1] 2 3 4 5