Recent Posts

Pages: [1] 2 3 4 5 6 ... 10
1
z/OS Server / Re: OAM Object Name Reference
« Last post by scottnys on Today at 12:22:21 PM »
First of all, I agree with Greg (he's my supervisor  ;D ) .
We have traditionally used various OAMs: 1year, 3years, 10years, etc.   Even if that would work, we wouldn't want to effect all of the other reports stored in that OAM - just the one APPLICATION Group in question.

if the report's retention were to be extended, we would only change all of the OAMs objects related to that ONE Application Group.  We would then change the CMOD Storage Set to then point to ANOTHER OAM with the desired, longer retention.  Future reports would then be stored there. 
2
z/OS Server / Re: OAM Object Name Reference
« Last post by rjchavez on Today at 12:10:23 PM »
Hi Scott.  I understand that your JCL is using the OSREQ CHANGE to remove or place a hold on an object.  My question is, why not use the OSREQ CHANGE ... MANAGEMENTCLASS(xxxxx) to update the management class of the object to a different retention?  The next time OSMC executes on the storage group, it would change the ODMCASDT date as per the retention period of the MC.
3
z/OS Server / Re: OAM Object Name Reference
« Last post by scottnys on Today at 12:00:27 PM »
I believe you are mis-interpreting the SYSIN card.  This is not a "change" to a management class, but a fully qualified REFERENCE to the document in question.  Remember they are paired.

OND.COLL.M1TEST.SGD03M1T.MCDM01     GAA.L4.FAAA <===
OND.COLL.M1TEST.SGD03M1T.MCDM01     GAA.L4.FAA1 <===
4
z/OS Server / Re: OAM Object Name Reference
« Last post by rjchavez on Today at 05:01:43 AM »
Ok, then why would the OSREQ CHANGE include the ability to update the MANAGEMENTCLASS?
5
z/OS Server / Re: OAM Object Name Reference
« Last post by Greg Ira on Today at 04:57:24 AM »
No., I wouldn't recommend doing that.  You'll confuse the heck out of OAM if you do.  OAM has already stored your objects in matching 4K and/or 32K tables for that management class.
6
z/OS Server / Re: Recommended DB2 on z/OS Service, V12
« Last post by Ed_Arnold on April 05, 2020, 09:06:52 AM »
Symptom:  S0C1 in ARSSOCKD after upgrade of Db2 to V12

Also could show up as Fault Analyzer IDI0002I Abend U3000 along with a SA03                                                                                           


Resolution: Db2 ODBC APAR PH11103:

ODBC WORKAROUND TO RETAIN TRAILING PERIOD IN THE CHAR REPRESENTATION OF DECIMAL COLUMNS

PTF UI63117 resolved the issue.
7
MP Server / OnDemand Load Data and odf service issue
« Last post by MHassan on April 05, 2020, 06:27:27 AM »
Hello,
After i installed ondemand V10.5, when i try to start the services load Data and distribution facility it show an error "the service did not not respond to start or control request in timely fashion"
so i searched for this error but what i get that i should add "ServicesPipeTimeout" in registry  , i followed this solution but nothing changes and the services keep show me the same error.

So any one have faced this issue and tried another solution and it worked from him ?
8
z/OS Server / Re: OAM Object Name Reference
« Last post by rjchavez on April 03, 2020, 02:19:18 PM »
Question:  If I update the management class in the OAM object directory for the documents in question, would that effectively change it's retention?
9
z/OS Server / Re: Maximum application groups mapped to a folder?
« Last post by scottnys on April 03, 2020, 12:01:26 PM »
Curious what a "large number of applications" would be? We've hit a high number of Index Data Tables when doing a search in a folder.  (160+ I seem to remember).  Forced to consolidate them. 

Gets a 13 record error "DB Error: {DB2 FOR OS/390}{ODBC DRIVER}{DSN11015}   DSNT408I SQLCODE = -101, ERROR:  THE STATEMENT IS TOO LONG OR TOO COMPLEX        DSNT418I SQLSTATE   = 54001 SQLSTATE RETURN CODE                                 DSNT415I SQLERRP    = DSNXOEA SQL PROCEDURE DETECTING ERROR                      DSNT416I SQLERRD    = -55  0  0  -1  0  0 SQL DIAGNOSTIC INFORMATION             DSNT416I SQLERRD    = X'FFFFFFC9'  X'00000000'  X'00000000'  X'FFFFFFFF'                  X'00000000'  X'00000000' SQL DIAGNOSTIC INFORMATION                      ERRLOC=5:10:2 -- SQLSTATE=54001, SQLCODE=-101, File=arsdoc.c, Line=2997"
10
z/OS Server / Re: OAM Object Name Reference
« Last post by scottnys on April 03, 2020, 10:16:57 AM »
It's been a couple of years since I had to do this.  My comment in the JCL  explains it.

THE WAY OAM IS CONFIGURED, THE EXPIRE PROCESS "CHECKS" WITH
THE MANAGEMENT CLASS FOR EXPIRATION.  THIS IS "TRUMPED" IF
THE (ODEXPDT) COLUMN IS OTHER THAN THE DEFAULT.
Pages: [1] 2 3 4 5 6 ... 10