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 ... 3 4 5 6 7 [8] 9 10 11 12 13 14
106
Tips and Tricks / ARSSLU utility - and how to run in batch on z/OS
« on: July 13, 2015, 09:28:23 AM »
Ref:  http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.administeringmp.doc/arsslu.htm?lang=en

"The ARSSLU command helps you audit your Content Manager OnDemand database for inconsistencies. Run this command only on the library server."

Sample JCL for running on z/OS:


//CREATE   EXEC PGM=BPXBATCH,REGION=0M                           
//STDPARM  DD *                                                 
SH                                                               
export DSNAOINI=/usr/lpp/ars/V9R5M0/config/cli.ini;             
export STEPLIB=DB2.V11R1M0.SDSNLOD2:DB2.V11R1M0.SDSNLOAD;       
/usr/lpp/ars/V9R5M0/bin/arsslu -I ARCH950 -c -v                 
/*                                                               
//SYSOUT DD SYSOUT=*                                             
//STDERR DD SYSOUT=*                                             
//STDOUT DD SYSOUT=*                                             
//**************************************************************
//POPULATE EXEC PGM=BPXBATCH,REGION=0M                           
//STDPARM  DD *                                                 
SH                                                               
export DSNAOINI=/usr/lpp/ars/V9R5M0/config/cli.ini;             
export STEPLIB=DB2.V11R1M0.SDSNLOD2:DB2.V11R1M0.SDSNLOAD;       
/usr/lpp/ars/V9R5M0/bin/arsslu -I ARCH950 -p -v                 
/*                                                               
//SYSOUT DD SYSOUT=*                                             
//STDERR DD SYSOUT=*                                             
//STDOUT DD SYSOUT=*                                             
//************************************************************** 
//ANALYZE  EXEC PGM=BPXBATCH,REGION=0M                           
//STDPARM  DD *                                                   
SH                                                               
export DSNAOINI=/usr/lpp/ars/V9R0M0/config/cli.ini;               
export STEPLIB=DB2.V11R1M0.SDSNLOD2:DB2.V11R1M0.SDSNLOAD;         
/usr/lpp/ars/V9R5M0/bin/arsslu -I ARCH950 -a -v                   
/*                                                               
//SYSOUT DD SYSOUT=*                                             
//STDERR DD SYSOUT=*                                             
//STDOUT DD SYSOUT=*                                             
//*************************************************************   
//DELETE   EXEC PGM=BPXBATCH,REGION=0M                           
//STDPARM  DD *                                                   
SH                                                               
export DSNAOINI=/usr/lpp/ars/V9R5M0/config/cli.ini;               
export STEPLIB=DB2.V11R1M0.SDSNLOD2:DB2.V11R1M0.SDSNLOAD;         
/usr/lpp/ars/V9R5M0/bin/arsslu -I ARCH950 -d -v </u/user33/yes;   
/*                                                               
//SYSOUT DD SYSOUT=*                                             
//STDERR DD SYSOUT=*                                             
//STDOUT DD SYSOUT=*                                             


Note 1: on z/OS you have to be at a minimum level of 8.5.0.10 or 9.0.0.6 or 9.5.0.2.

Note 2: /u/user33/yes is a file that contains the character "y", nothing else.  It's to respond to what would ordinarily be an interactive prompt.

Ed

107
Ref:   http://www-01.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.administeringmp.doc/mustgather.htm?lang=en

"You can use ARSSUPPORT, a Java™ based tool to gather diagnostic information such as log entries. This tool is especially helpful when you need to report problems to IBM® service.
The ARSSUPPORT utility is delivered in the arssupport.jar file."

Here's an example of how I run it in batch on z/OS:


//STEP1   EXEC PGM=BPXBATCH,REGION=0M                                 
//STDPARM DD *                                                       
SH                                                                   
export JAVA_HOME=/usr/lpp/java/J7.0_64;                               
export PATH=/bin:/usr/lpp/ars/V9R0M0/bin:/usr/lpp/java/J7.0_64/bin;   
java -jar /usr/lpp/ars/V9R0M0/jars/arssupport.jar -o /ars/modwekcache
-z /usr/lpp/ars/V9R0M0/                                               
-l -u user33 -p mypwyeah -I ARCH900 -m 6000 -v;                       
//SYSOUT   DD SYSOUT=*                                               
//STDERR   DD SYSOUT=*                                               
//STDOUT   DD SYSOUT=*                                               


Ed

108
I was asked for a brief checklist for items in addition to the migration instructions, sharing it here:

  • If migrating to V8.5 or above for the first time, are you comfortable with the ARS_ORIGINAL_CODEPAGE setting you'll be using?
     
  • do you understand why you see this message ARS0220I Server code page is 1200 ?   Note that your ARS_ORIGINAL_CODEPAGE setting is probably not 1200.
     
  • are you using the new ARSSOCKD parms of "-S -I [instance] -v"?

    Reference:

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

     
  • Is this CMOD instance on the same LPAR or on a different LPAR than your test system?  If on a different LPAR, ensure that your OMVS settings are the same or greater on the new LPAR.   (operator commands   D OMVS,L and D OMVS,O to check)
     
  • If not already in production, have all DB2 PTFs from the following web pages at least received into your DB2 SMP/E:

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

    http://www.odusergroup.org/forums/index.php?topic=1318.0
     
  • Have all CMOD PTFs received into your CMOD SMP/E.  Ensure you have received the CMOD PTF for APAR PI42688 which corrects an error in an error message
     
  • the most common error reported to Level 2 after an upgrade from V8.4.1 or before to V8.5 or above is the restriction that the OS/390 Indexer will now report when an index value is not found and no default value is specified.

    The error message you receive when encountering this will be, for example "8 fields submitted by the indexer, 12 expected"

Ed

109
PI41142 

AFTER APPLICATION OF UI23134, BATCH JOBS THAT INVOKE ACIF       
MORE THAN 10 TIMES FAIL WITH RC12 X'C'.


Do not APPLY UI23134 (APAR PI16171) until it gets resolved.

ARSYSPIN and ARSLOAD - when it's running as a started task - will hit this problem.

Ed

110
JOB card, of course

The contents of '/ars/tmp/yes' is the letter y  ---- that's all.  It's to respond to the prompt.



//COMMENT  EXEC  PGM=IKJEFT01,REGION=0M,                         
//            DYNAMNBR=200                                       
//SYSPROC  DD  DSN=SYS1.SBPXEXEC,DISP=SHR                         
//*                                                               
//SYSTSPRT DD  SYSOUT=*                                           
//*                                                               
//SYSTSIN  DD  *                                                 
 oshell logger -d1 drop ARSRES index                             
/*                                                               
//DROPINDX EXEC PGM=BPXBATCH,REGION=0M,                           
// PARM='SH  /usr/lpp/ars/V9R0M0/bin/arsdb -I ARCH900 -efv ARSRES'
//*                                                               
//STEPLIB  DD DISP=SHR,DSN=DB2.V11R1M0.SDSNLOAD                   
//         DD DISP=SHR,DSN=DB2.V11R1M0.SDSNLOD2                   
//SYSPRINT DD SYSOUT=*                                           
//SYSOUT   DD SYSOUT=*                                           
//STDIN DD PATH='/ars/tmp/yes',PATHOPTS=(ORDONLY)                 
//STDERR   DD SYSOUT=*                                           
//STDOUT   DD SYSOUT=*                                           
//STDENV DD *                                                     
_BPXK_JOBLOG=STDERR                                               
/*                                                               
//CREATE   EXEC  PGM=IKJEFT01,REGION=0M,                         
//            DYNAMNBR=200                                       
//SYSPROC  DD  DSN=SYS1.SBPXEXEC,DISP=SHR                         
//*                                                               
//SYSTSPRT DD  SYSOUT=*                                       
//*                                                           
//SYSTSIN  DD  *                                             
 oshell logger -d1 create ARSRES index                       
 oshell /usr/lpp/ars/V9R0M0/bin/arsdb -I ARCH900 -rv ARSRES   
 oshell logger -d1   update statistics                       
 oshell /usr/lpp/ars/V9R0M0/bin/arsdb -I ARCH900 -mv         
 oshell logger -d1   ending ARSRES maint                     
//*   

111
   JOB card
//STEP1   EXEC PGM=BPXBATCH,REGION=0M                     
//STDPARM DD *                                             
SH                                                         
export DSNAOINI=/path/to/cli.ini;                     
export STEPLIB=DB2.V11R1M0.SDSNLOD2:DB2.V11R1M0.SDSNLOAD; 
cd /directory/to/write/to;                                     
/usr/lpp/ars/V9R0M0/bin/arsdb -I ARCH900 -vx ARSHOLD;     
/usr/lpp/ars/V9R0M0/bin/arsdb -I ARCH900 -vx ARSHOLDMAP;


The output will be written to /directory/to/write/to

112
z/OS Server / Exporting Applications and Application Groups Via ARSXML
« on: April 27, 2015, 09:45:49 AM »
I was recently asked how to export an app and appgroup with ARSXML.

First off, check out this link.  "Listing 1" shows the format for each type of object to export.

http://www.ibm.com/developerworks/data/library/techarticle/dm-0510wagner/

I wanted to list out one app/app group so I created the following file:

<?xml version="1.0" encoding="IBM-1047"?>                                   
<onDemand xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"             
                xsi:noNamespaceSchemaLocation="../ondemand.xsd">           
                                                                           
   <applicationGroup name="Daily sales invoices">                           
   </applicationGroup>                                                     
   <application name="Daily sales invoices" appGroup="Daily sales invoices">
   </application>                                                           
                                                                           
</onDemand>                                                                 


The example above is for listing out the "Daily sales invoices app and appgroup from the ODF IVP.  (Yes, in this case the application name and the appGroup are the same.)

Then one up from that directory I copied the .../bin/xml/ondemand.xsd file pointed to in the example above.

Then I ran the following JCL:

//STEP1    EXEC PGM=BPXBATCH,REGION=0M           
//SYSPRINT DD SYSOUT=*                           
//SYSOUT   DD SYSOUT=*                           
//STDPARM  DD *                                 
PGM /usr/lpp/ars/V8R5M0/bin/arsxml               
export                                           
-h ARCH850 -u odv733 -p cmodrocks -v             
-d /u/odv733/t/                                 
-i                                               
application.ebcdic.xml                           
-o                                               
/u/odv733/t/exportap.ebcdic.xml                 
-w IBM-1047                                     
/*                                               
//ARSBIN     DD PATH='/usr/lpp/ars/V8R5M0/bin'   
//SYSOUT     DD SYSOUT=*                         
//STDERR     DD SYSOUT=*                         
//STDOUT     DD SYSOUT=*                         
//SYSUDUMP   DD SYSOUT=*                         


-d = source directory where the input xml files lives

-i = the name of the input xml file

-o = where the output gets written to

-w IBM-1047 = readable on z/OS.  Otherwise it comes out as ASCII and you have to use iconv or whatever to convert it into something readable.  (ugh)

Ed


113
z/OS Server / Change In JCL Parms For ARSADMIN In 9.5.0
« on: April 13, 2015, 06:16:22 PM »
I'm running the following on a z/OS 1.13 system.

Consider the following JCL which I use to unload the load from the ODF IVP:

//STEP1    EXEC PGM=ARSADMIN,REGION=0M,               
//   PARM=('/-V //DD:IN -u odadmin  -p blahblah')     
//STEPLIB  DD DISP=SHR,DSN=ARS.ARSV950.SARSLOAD       
//SYSPRINT DD SYSOUT=*                                 
//SYSOUT   DD SYSOUT=*                                 
//IN       DD *                                       
unload                                                 
-h                                                     
ARCH950                                               
-g                                                     
"Daily sales invoices"                                 
-L                                                     
5052-1-0-5FAA-0-0-5053                                 
/*                                                     
//ARSBIN     DD PATH='/usr/lpp/ars/V9R5M0/bin'         
//SYSPRINT   DD SYSOUT=*                               
//SYSOUT     DD SYSOUT=*                               
//STDERR     DD SYSOUT=*                               
//STDOUT     DD SYSOUT=*   


In V9.5 of CMOD the "-V" parm has been removed from the list of optional parms. 

Reference:  http://www-01.ibm.com/support/knowledgecenter/SSQHWE_9.5.0/com.ibm.ondemand.administeringzos.doc/dodad002.htm 

If I run this JCL on V9.5 I get the following in SYSOUT:

********************************* TOP OF DATA ********************************************
ARS1000I Usage: arsadmin  unload | store | retrieve | import | compress | decompress | icu
 Version:  9.5.0.1                                                             
******************************** BOTTOM OF DATA ******************************************


Okay ... I'll just put all of those parms in the PARM= field.

NO GOOD!

Now I get the following error:

IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD

IF you're on z/OS 2.1 the parm field has been expanded and z/OS can handle a parm field of that length.

IF you're on z/OS 1.13 or earlier the length of the parm field required to unload the ODF IVP is greater than the operating system can handle.


How will I circumvent this?

Well, of course I could unload from the admin client but that's the easy way out. 

I want to do this in batch.


What I'm going to do is via the admin client rename "Daily sales invoices" to just DSI for now.

Then I'll need to revisit the whole ODF IVP to look into changing "Daily sales invoices" to DSI...

...or look into getting my test system upgraded to z/OS V2.1. 

Ed





                         


114
z/OS Server / USEZOSV1R9RULES(YES/NO)
« on: April 03, 2015, 12:56:45 PM »
A DB2 performance enhancement shipped with z/OS that is often overlooked is the setting for USEZOSV1R9RULES.

It changes the memory allocation algorithm and is advertised as being helpful particularly for large DB2 shops.


If you go to the z/OS operator's console and issue D DIAG you'll probably get an answer that looks like this:

IGV007I 15.43.25 DIAG DISPLAY
VSM TRACK CSA(ON) SQA(ON)   
VSM TRACE GET(OFF) FREE(OFF)
VSM ALLOWUSERKEYCSA(NO)     
VSM BESTFITCSA(NO)           
VSM USEZOSV1R9RULES(YES)     
TRAPS NAME()                 
CBLOC                       
  VIRTUAL24()               
  VIRTUAL31()               
REUSASID(YES)               
AUTOIPL SADMP(NONE) MVS(NONE)


Note the USEZOSV1R9RULES setting --- YES is the default.

I'm not going to go into an explanation - google and you'll find out all you need to know.


--- HOWEVER ---

There is risk with this setting.  The reason the default is the old way of memory allocation is because some programs are not well-behaved.

For example, this APAR for Netview Distribution Manager:

PI20869  NetView Distribution Manager

FOR Z/OS 1.10 AND HIGHER, USEZOSV1R9RULES(YES) IN SYSTEM PARMLIB
DIAGXX MEMBER IS REQUIRED     

ERROR DESCRIPTION:                                               
The NvDM code needs to have storage allocated in the way         
that the USEZOSV1R9RULES(YES) parameter does - this value is     
the default value.  USEZOSV1R9RULES(NO) must not be coded or     
abends or other problems may occur.   
                           
To document this restriction, the following change will be       
made to the Tivoli NetView Distribution Manager for MVS IBM     
Installation and Customizationmanual ( Release 7 SH19-6794-06 ) 
in appendix A (Installation Requirements):     
                 
After the sentence which ends with "see the target               
system requirements specification in the NetView DM for MVS Base
ProgramDirectory."  add the following:                           
.                                                               
Note: For z/OS 1.10 and higher, the DIAGxx parameter             
USEZOSV1R9RULES(YES) is required.  This is the default value.   
Coding USEZOSV1R9RULES(NO) will cause unpredictable results.



If you think this would be of benefit to you then thoroughly test before implementing in production.

CMOD has no problem with this...it's been tested with all supported releases on z/OS.

Ed

115
Tips and Tricks / Displaying Memory Available
« on: March 22, 2015, 03:24:36 PM »
1. Run the following JCL:

//STEPHARD EXEC PGM=BPXBATCH,REGION=0M   
//STDPARM  DD *                           
SH ulimit -a                             
//SYSPRINT DD SYSOUT=*                   
//STDERR   DD SYSOUT=*                   
//SYSOUT   DD SYSOUT=*                   
//SYSPRINT DD SYSOUT=*                   

Example STDOUT:

core file         unlimited         
cpu time          86375             
data size         unlimited         
file size         unlimited         
stack size        unlimited         
file descriptors  64000             
address space     1870824k           
memory above bar  17592186040320m   

a) spice this up by using different REGION=x sizes to see the difference

b) doubly spice this up by adding this to the bottom of the JCL:

//STDENV DD *                         
_CEE_RUNOPTS=RPTSTG(ON),RPTOPTS(ON)   
/*                                   

STDERR on my system now has (1) a listing of all of the default LE run time options, and (2) storage report information such as STACK and HEAP sizes


2. This EXEC I shamelessly stole from the IBM-MAIN listserver group - works just great out in TSO or inside OMVS:

/* REXX *** */                                                               
 IF SYSCALLS('ON')>3 THEN                                                     
    DO                                                                       
    SAY 'Unable to establish the SYSCALL environment'                         
    SAY 'Return code was 'RC                                                 
    RETURN                                                                   
    END                                                                       
 ADDRESS SYSCALL                                                             
/* display current limits for OMVS resources */ Say 'Maximum amount of CPU = 
time (in seconds) used by a process.'                                         
 CALL dolim 'rlimit_cpu'                                                     
Say 'Maximum files size (in bytes) created by a process.'                     
 CALL dolim 'rlimit_fsize'                                                   
Say 'Maximum number of open file descriptors for a process.'                 
 CALL dolim 'rlimit_nofile'                                                   
Say 'Maximum address space size for a process.'                               
 CALL dolim 'rlimit_as'                                                       
Say 'Maximum size (in bytes) of a core dump created by a process.'           
 CALL dolim 'rlimit_core'                                                     
 exit 0                                                                       
 dolim: ,                                                                     
 arg v .                                                                     
/* return current limits for resource */               
 num=value(v)                                         
 "getrlimit "num" rv."                                 
 SAY 'Resource='v'('num') current='rv.1 'maximum='rv.2
 Say ' '                                               
 return                                               


Produces output that looks like this:

Maximum amount of CPU =time (in seconds) used by a process.       
Resource=RLIMIT_CPU(0) current=2147483647 maximum=2147483647     
                                                                 
Maximum files size (in bytes) created by a process.               
Resource=RLIMIT_FSIZE(1) current=2147483647 maximum=2147483647   
                                                                 
Maximum number of open file descriptors for a process.           
Resource=RLIMIT_NOFILE(6) current=64000 maximum=64000             
                                                                 
Maximum address space size for a process.                         
Resource=RLIMIT_AS(5) current=1033412608 maximum=2147483647       
                                                                 
Maximum size (in bytes) of a core dump created by a process.     
Resource=RLIMIT_CORE(4) current=2147483647 maximum=2147483647     

Ed




116
Problem:  brought up a new test instance and we want to copy over all of the userids.

Solution: use ARSXML, but it's not quite that straightforward

Note:  This assumes that you used the wizard to set up the new instance and you have a user admin pw sysadmin set up in the new instance.


This is one way to do it on z.

1. Create the following USS file:

********************************* Top of Data *****************************
<?xml version="1.0" encoding="IBM-1047"?>                                 
<onDemand xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"           
xsi:noNamespaceSchemaLocation="/usr/lpp/ars/V9R5M0/bin/xml/ondemand.xsd"> 
                                                                           
                                                                           
<!--  This will export all of the users  -->                               
                                                                           
<user name="_ALL"/>                                                       
                                                                           
</onDemand>                                                               
******************************** Bottom of Data ***************************


2. Run the following JCL to export all users to the file allusers.ebcdic.xml

//STEP1    EXEC PGM=BPXBATCH,REGION=0M                 
//SYSPRINT DD SYSOUT=*                                 
//SYSOUT   DD SYSOUT=*                                 
//STDPARM  DD *                                         
PGM /usr/lpp/ars/V8R5M0/bin/arsxml                     
export                                                 
-h ARCH850 -u arnie  -p password -v                   
-d /u/odv733/xml/                                       
-i                                                     
exportallusers.xml                                     
-o                                                     
/u/odv733/xml/allusers.ebcdic.xml                       
-w IBM-1047                                             
/*                                                     
//ARSBIN     DD PATH='/usr/lpp/ars/V8R5M0/bin'         
//SYSOUT     DD SYSOUT=*                               
//STDERR     DD SYSOUT=*                               
//STDOUT     DD SYSOUT=*                               
//SYSUDUMP   DD SYSOUT=*       


3. Ensure that the ars.ini for the new instance has

SRVR_FLAGS_SECURITY_EXIT=0                         

4. If you try to import that file it will fail because there are no passwords in there so you can do a change all to add a dummy password field to allusers.ebcdic.xml:

<user name="BRIAN" password="password" updateDate=...
</user>                                             
<user name="ED" password="password" updateDate=...
</user>                                             
<user name="LARRY" password="password" updateDate=...
</user>                                             
<user name="LAMIES" password="password" updateDate=...
...


5. Now you can import the users with this JCL

//STEP1    EXEC PGM=BPXBATCH,REGION=0M             
//SYSPRINT DD SYSOUT=*                             
//SYSOUT   DD SYSOUT=*                             
//STDPARM  DD *                                     
PGM /usr/lpp/ars/V9R5M0/bin/arsxml                 
add                                                 
-h ARCH950 -u admin   -p sysadmin -v -e c           
-d /u/odv733/xml/                                   
-i                                                 
allusers.ebcdic.xml                                 
/*                                                 
//ARSBIN     DD PATH='/usr/lpp/ars/V9R5M0/bin'     
//SYSOUT     DD SYSOUT=*                           
//STDERR     DD SYSOUT=*                           
//STDOUT     DD SYSOUT=*                           
//SYSUDUMP   DD SYSOUT=*             
               

6. Change ars.ini to
SRVR_FLAGS_SECURITY_EXIT=1

7. Restart ARSSOCKD and voila!  All userids are now in the new instance and their passwords will be verified against your external security manager.

Ed

118
z/OS Server / z/OS V2.1 OAM PTF is PE, fixed in 1406 PUT
« on: December 15, 2014, 08:05:34 AM »
If you're rolling out UA72482, make sure you have the following on your z/OS 2.1 system:

PTF#     Reason Listed       Size-KB PUT  Hiper FMID      
-------- ------------------- ------- ---- ----- ---------
UA72482                           70 1403  NO   HDZ2210  
UA73899  PE-RES of UA72482        40 1406  NO   HDZ2210  


Ed

119
OD/WEK & JAVA API / Update ODWEK First, Then Update Java
« on: November 28, 2014, 08:16:07 AM »
Horse, then cart.

Occasionally we still see people getting bit by newer Java requiring newer ODWEK.

Bottom line:  Upgrade ODWEK to 9.0.0.3 or 8.5.0.9 *before* installing Oracle Java 7 Update 25.

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

Ed


120
MP Server / EoS CMOD 8.5 April 30th, 2016
« on: November 21, 2014, 09:32:42 AM »
Software withdrawal and support discontinuance: IBM Content Manager OnDemand for Multiplatforms V8.5, and selected part numbers for AFP2WEB for IBM Content Manager OnDemand i - Replacements available

http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS914-242

Ed

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