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 ... 6 7 8 9 10 [11] 12 13 14
151
If you're like us we run multiple copies of OnDemand.

When we logon with the admin or user client we use the ARS_MESSAGE_OF_THE_DAY parm to display a message.

http://publib.boulder.ibm.com/infocenter/cmod/v8r5m0/index.jsp?topic=%2Fcom.ibm.ondemand.configuringzos.doc%2Fars3u371118.htm

In our messages of the day we say which system we're logging on to.

This is good on all platforms.


152
z/OS Server / z/OS shops on 8.5.0 please check the PSP bucket for HIPERs
« on: October 11, 2012, 12:55:33 PM »
In particular, the last two APARs, PM62376 and PM73809, have bitten multiple shops.

PM62376 says it's a high cpu problem, but underneath it's an 0C4 and subsequent to the PSP bucket update it was found that the problem can manifest itself in different ways.   

Fortunately neither of these HIPERs involve data loss.

I recommend you roll out both soonest.

https://www-304.ibm.com/support/docview.wss?dc=DB540&rs=1209&uid=isg1_ODMP850_H272850&cs=UTF-8&lang=all&loc=en_US

Ed

153
New fix available for all releases of CMOD:

PM62093

PROBLEM SUMMARY:                                               
****************************************************************
* USERS AFFECTED: All Content Manager OnDemand installing      *
*                 OA38944                                      *
****************************************************************
* PROBLEM DESCRIPTION: When gathering SPOOL files, ARSYSPIN    *
*                      will sort the SPOOL files by the JES    *
*                      dataset name.  When OA38944 is          *
*                      installed, and if greater than 10       *
*                      million spool files are created by a    *
*                      specific job, that sort will not sort   *
*                      correctly                               *
****************************************************************

++ HOLD(UK8187x) SYS FMID(H272841) REASON(ENH) DATE(12261)         
   COMMENT                                                         
    (Cross product dependancy for OA38944.  This PTF changes the   
     way ARSYSPIN does sort and should be installed before         
     OA38944.).   


OA38944:

PROBLEM SUMMARY:                                               
****************************************************************
* USERS AFFECTED: All users of HJE7750, HJE7760, HJE7770, and  *
*                 HJE7780.                                     *
****************************************************************
* PROBLEM DESCRIPTION: NEW FUNCTION:  Support for greater than *
*                      10M spin data sets.                     *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
JES data sets are limited to 10 million per job.  Long running 
jobs that create spin data sets can reach this limit.  Jobs that
reach this limit require to be shut down and restarted.  The   
support added via this APAR extends the limit to 4 billion data
sets that can be created during the life time of a job.                                                         

154
Tips and Tricks / OAM IVP and Initial Problem Determination
« on: September 12, 2012, 08:03:02 AM »
Say you get a CMOD error after doing some OAM set up work.

How do you know whether to start your problem determination with CMOD or with OAM?

SYS1.SAMPLIB(CBRSAMIV) is the OAM IVP.

If it doesn't work, then your local OAM support or, if needed, IBM OAM support should be contacted first

Ed

Quote
//* THIS SAMPLE JOB INVOKES THE OSREQ COMMAND PROCESSOR TO PERFORM  
//* THE FOLLOWING ACTIONS:                                          
//*                                                                  
//* 1. STORE A 1 MB (1048576) OBJECT.                                
//*                                                                  
//* 2. ISSUE AN OSREQ QUERY TO LIST THE OAM DIRECTORY INFORMATION.  
//*                                                                  
//* 3. ISSUE A LISTCAT COMMAND TO LIST THE COLLECTION NAME ENTRY    
//*    FROM THE ICF CATALOG.                                        
//*                                                                  
//* 4. ISSUE AN OSREQ CHANGE REQUEST TO CHANGE THE RETENTION PERIOD  
//*    ASSOCIATED WITH THE OBJECT TO 365 DAYS.                      
//*                                                                  
//* 5. ISSUE AN OSREQ QUERY TO LIST THE OAM DIRECTORY INFORMATION.  
//*                                                                  
//* 6. ISSUE AN OSREQ RETRIEVE TO RETRIEVE THE PRIMARY COPY OF THE  
//*    AND CHECK TO SEE IF IT CONTAINS THE PRE-DEFINED PATTERN DATA.
//*                                                                  
//* 7. ISSUE AN OSREQ DELETE REQUEST TO DELETE THE OBJECT.
         

155
z/OS Server / CMOD V9 on z/OS Install Notes
« on: September 10, 2012, 12:44:15 PM »
My initial DLIB allocations for AARSOBJ1, AARSHAS1, AARSHMS1 were too small. 

I made them the same as what I had allocated for 8.x and I was good to go.


157
This is how I usually run my ARSLOADs in batch:

//STEP1     EXEC PGM=ARSLOAD,REGION=0M,                         
//       PARM=('/-h ARCH850 -u odadmin -p hahahaha -nfv         
//              -g "Daily sales invoices" /tmp/salesinvoice')   
//STEPLIB    DD DISP=SHR,DSN=ARS.ARSV850.SARSLOAD               
//           DD DISP=SHR,DSN=DSN.DB2VA10.SDSNEXIT               
//           DD DISP=SHR,DSN=DSN.DB2VA10.SDSNLOAD               
//           DD DISP=SHR,DSN=DSN.DB2VA10.SDSNLOD2               
//ARSBIN     DD PATH='/usr/lpp/ars/V8R5M0/bin'                 
//SYSPRINT   DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=134,BLKSIZE=134) 
//*YSTCPT    DD SYSOUT=*                                         
//SYSOUT     DD SYSOUT=*   

Especially when I add trace parms to the //PARM=('/-h blah blah') statement I'll end up with more characters than it'll accept.

So in that case I run the load from BPXBATCH:

//**************************************************************
//STEP1   EXEC PGM=BPXBATCH,REGION=0M                           
//STDIN  DD PATH='/u/odv733/arnold.in',PATHDISP=(KEEP)           
//SYSOUT DD *                                                   
//STDERR DD PATH='/u/odv733/bpxbatch.err',PATHMODE=SIRWXU,       
//       PATHOPTS=(OWRONLY,OCREAT,OTRUNC),PATHDISP=(KEEP,DELETE)
//STDOUT DD PATH='/u/odv733/bpxbatch.out',PATHMODE=SIRWXU,       
//       PATHOPTS=(OWRONLY,OCREAT,OTRUNC),PATHDISP=(KEEP,DELETE)
//STDENV DD  *                                                   
**************************** Bottom of Data *********************

Then what's in STDIN (the arnold.in file) is this:

********************************* Top of Data ***********************
/usr/lpp/ars/V8R5M0/bin/arsdate -g                                   
/usr/lpp/ars/V8R5M0/bin/arsload -h ARCH850 -u odadmin -p blahblah -nfv -g "Daily sales invoices" /tmp/salesinvoice
**************************** Bottom of Data *************************

I throw the arsdate -g in there just for a datestamp on top of bpxbatch.out, which then looks like this:

********************************* Top of Data ***********************
Today:.08/31/12                                                     
arsload: Using /u/odv733 for temporary files                         
arsload: Processing file >/tmp/salesinvoice<                         
arsload: Load Version <8.5.0.5> Operating System <z/OS> <03.23.00>   
arsload: Server Version <8.5.0.5> Operating System <z/OS> <03.23.00>
arsload: 08/31/12 14:05:23 -- Loading started, 39486 bytes to process
blah blah blah
*****************************                                   

158
If you see messages like this:

ARS0020E xxxxxxxxx SM ERROR: ARSMVSRE: 0000000B(00000008-2C040100) 
 HLQ1.OAM.D730T99.ODXX0000(MAA.L957.FAAF), RETURN CODE=11, REASON=0
, FILE=ARSSMSMS.CPP, LINE=995  SRVR->PRIMO_2B 111.111.11.11<-     

ARS0024E SLCPAPI OBJECT >370< IN APPLICATION GROUP >MAA< NOT FOUND IN
 NODE >HLQ1.OAM.D730T99.ODXX0000<  SRVR->PRIMO_2B 111.111.11.11<


Is there SPUFI code to find orphaned index entries without OAM objects?
                                                             
There are already SPUFI procedures to find orphaned OAM objects with no index entries. 


The answer is there is no easy, automated way to do this.                               
                                                                       
After much discussion, this was the consensus:                             
                                                                       
Attack this from the AG.                                       
                                                                       
First, you would have to build a list of all the unique object names   
from AG Data table.  You could then extract all the object names for the
AG from OAM.  After you have sorted both files into ascending sequence,
you could compare the files finding object names in CMOD and not in OAM.
                                                                       
For each of the orphaned indexes, you would have build an ARSMAINT     
command to delete the index row.         


I know, not automated or very neat, but perhaps someday someone will improve upon this.                                                                                         

159
z/OS Server / ICH408I Messages After Upgrading to 8.5 on z/OS
« on: August 28, 2012, 01:41:16 PM »
If you get this:

 ICH408I USER(ARSSERV2) GROUP(ODCMARS ) NAME(XXXXXXXX)  353
    353               CSFIQF CL(CSFSERV )
    353               INSUFFICIENT ACCESS AUTHORITY
    353               FROM * (G)
    353               ACCESS INTENT(READ   )  ACCESS ALLOWED(NONE   )

The reason is:

One of the enhancements with OnDemand 8.5 is the encryption of passwords
with AES-128, both over the wire and in the OnDemand data base.   This
gets done automagically if CSF is available and providing AES-128
service.

How does OnDemand find out if AES-128 is available?   It calls CSFIQF -
ICSF Query Facility callable service.  It turns out that even though
it's a query type service, you can lock it down via RACF.  We use CSFIQF
and must be permitted to it.

OnDemand will get along just fine without the permission but you will
get error messages from RACF, and OD will use the pre 8.5 methods on the
passwords over the wire and in the data base.

160
z/OS Server / Sample ARSPDOCI JCL
« on: August 22, 2012, 07:37:41 AM »
I know the JCL for this job is a little obtuse.  Here's a sample I have.  If anyone else has samples please share.

Ed

//ARSPDOCI EXEC PGM=ARSPDOCI,REGION=0M,                   
// PARM='/parmdd=//DD:PAR inputdd=//DD:IN'                 
//STEPLIB  DD DSN=ARS.ARSV840.SARSLOAD,DISP=SHR           
//PAR      DD DISP=SHR,DSN=ODUSER.TESTPDF.TEMP.CNTL(P88650)
//IN       DD DISP=SHR,DSN=ODUSER.P88650.PDF80             
//*                                                       
//SYSOUT   DD SYSOUT=*                                     
//SYSPRINT DD SYSOUT=*                                     
                                                           
                                                           
 BROWSE    ODUSER.TESTPDF.TEMP.CNTL(P88650) - 01.19   L   
 Command ===>                                             
********************************* Top of Data *********   
COORDINATES=IN                                             
TRIGGER1=UL(7.80,9.14),LR(7.69,9.54),*,'PAGE:'             
FIELD1=UL(7.80,9.14),LR(7.69,9.54),0,(TRIGGER=1,BASE=0)   
INDEX1='PAGE',FIELD1,(TYPE=GROUP)                         
INDEXSTARTBY=2                                             
INDEXDD=/u/oduser/P88650.ind                               
OUTPUTDD=/u/oduser/P88650.out                             
******************************** Bottom of Data *******   

I haven't tested this, but I believe if your IN is in an HFS dataset, then the DD def for that
would be                                                               
                                                                       
//IN    DD PATH='/tmp/print.out',                                       
//            PATHOPTS=(ORDONLY),PATHDISP=(KEEP)                       

161
http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/3/897/ENUS212-273/index.html&lang=en&request_locale=en

IBM Content Manager OnDemand for Multiplatforms V9.0 adds full text search, advanced systems monitoring, security, performance, and usability enhancements

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

Content Manager OnDemand V8.4.1.x ODWEK CGI/Servlet issue with CacheFile
authentication against 8.5.x OnDemand servers
     

Problem(Abstract)                                                         
                                                                           
Running a Content Manager OnDemand Web Enablement Kit (ODWEK) CGI/Servlet 
version prior to PTF 8.4.1.8 against an 8.5.x OnDemand server can result in
increased logon/logoff traffic to the OnDemand Server due to an issue with
authentication during CacheFile restoration.

163
Tips and Tricks / Looking Up Some Of Those Error And Reason Codes
« on: June 08, 2012, 02:05:14 PM »
Q: If you have a CEEDUMP, how do you look up the following error codes?

   Thread Id .... 1972B00000000000 Errno ...... 129 Errnojr .... 0594003D 
 CEE3846I CEEDUMP Processing completed.                                   


A1:  The 129 comes from the errno.h file:

(From a USS command line):

 >grep 129 /usr/include/errno.h
          #define ENOENT          129  /* No such file or directory  */

A2:  The Errnojr you can look up via the BPX Message Text TSO command

(From an ISPF command prompt):
 
Command ===> tso bpxmtext 0594003D

BPXFVLKP 04/23/09                                      
JRDirNotFound: A directory in the pathname was not found

Action: One of the directories specified was not found.  Verify that the name
specified is spelled correctly.  


Another example - say you're running arsload and you get the following:

 arsload: 11/10/11 17:27:34 -- Loading started, --UNKNOWN-- bytes to
 process
 error- Unable to write 18868906 bytes, file
 /fooTEST/foo_INTEG/ars/tmp/Nov1020111727365032101F30000000000.001,
 errno 133 errno2 ef07604a, line 946
 Loaded 0 rows into the database
 arsload: 11/10/11 17:27:36 Loading failed
 arsload: Processing failed for file



>grep 133 /usr/include/errno.h                               
         #define ENOSPC          133  /* No space left on device    */
        #define EDQUOT         1133  /* Reserved.                  */

(Yeah, two hits, but the 133 is the one we're worried about)

(Then we check that 8 character hexadecimal code)

Command ===> tso bpxmtext ef07604a

Description: General file write error.                         
                                                               
Action: Check the return code to determine why the write failed.

(In this case the errno.h reason code is more descriptive of the problem)

164
z/OS Server / HIPER APAR/PTFs for all 8.4.0 and above released today
« on: April 13, 2012, 06:51:23 AM »
http://www-01.ibm.com/support/docview.wss?uid=swg27024735

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

In short, the OS/390 indexer, under an exceptionally rare condition has the potential to generate incorrect indexing values and/or some lines of the report not getting stored.

I can't say it any better than the doc above.

PM58481

IF FMID(H272841) THEN UK77812
IF FMID(H27284A) THEN UK77811
IF FMID(H272850) THEN UK77813

165
z/OS Server / ACIF Version 4.3.0 is the only supported Version/Release
« on: March 23, 2012, 09:07:40 AM »
ACIF comes out of the InfoPrint company and it wasn't very well publicized but all releases of Version 2 ACIF are now out of support.

Pages: 1 ... 6 7 8 9 10 [11] 12 13 14