Show Posts
106
Tips and Tricks / Checklist for New CMOD on z Installations
« on: November 30, 2021, 11:43:52 AM »
Just some things I came up with that too frequently get overlooked by new CMOD customers on z:
On the EXEC PGM=ARSSOCKD, the “/” in the parm= line is required to ensure that LE doesn’t try to read CMOD parms and vice versa
XXONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,MEMLIMIT=NOLIMIT,
XX* PARM='TRACE(ON,15M,,LE=8)/-S -I ARCH1010 -v'
XX* PARM='/-S -I ARCH1010 -v'
XX* PARM=('ENVAR(_CEE_HEAP_MANAGER=CELQMCHK)/-S -I ARCH1010 -v')
XX* PARM='/-S -I ARCH1010 -v -1 /tmp/ela.trc -2 ALL=15'
XX*PARM='/-S -I ARCH1010 -v -d "keystore_location=CKDS,keystore_mkl=*"
XX PARM=('ENVAR(LDAP_DEBUG=2147483647)/-S -I ARCH1010 -v ')
XX* PARM='RPTOPTS(ON)/-S -I ARCH1010 -v'
XX* PARM='DYNDUMP(IBM),RPTOPTS(ON)/-S -I ARCH1010 -v'
XX* PARM='RPTOPTS(ON),RPTSTG(ON)/-S -I ARCH1010 -v'
XX* PARM=('ENVAR(_EDC_DLL_DIAG=TRACE)/-S -I ARCH1010 -v')
On z, if your back end is OAM, it’s so fast you don’t probably don't need cache except for handling the system log (contact L2 if want you an explanation).
You probably don't want to load exclusively to virtual tape. It isn’t fast enough to handle a heavy load of ‘hot’ data.
When defining a test application group, the default number of rows for a table is probably way too large. From the first screen in defining a new app group, select Advanced. On the next screen is the default, 10,000,000 rows, which is probably way too big and a waste of space.
Don’t ever change the permissions on the cache filesystem.
Example of config link to ars.ini file --- need that symlink:
Type Perm Changed-PST8PDT ------Size Filename
_ Dir 755 2021-09-16 09:54 8192 bin
_ Dir 755 2021-04-16 11:27 8192 www
_ Dir 755 2021-04-16 11:23 8192 midserver
_ Dir 755 2021-04-16 11:22 8192 jars
_ Dir 755 2021-04-16 11:22 8192 samples
_ Dir 755 2020-11-25 08:17 8192 locale
_ Dir 755 2020-03-31 11:58 8192 ..
_ Syml 777 2020-02-26 07:49 8 config <------
_ Dir 755 2020-02-26 05:28 8192 .
Ars.ini file has to have a very first line with x’AD’ and x’BD’:
***********************
Ý@SRV@_ARCH850¨
HOST=mvsxxx
PROTOCOL=2
with hex on
Ý@SRV@_ARCH850¨
A7EDE76CDCCFFFB
DC295CD1938850D
That first line is the CMOD instance name, used with arsload. Which is different from the “SERVER_INSTANCE” which refers to the database name
Ý@SRV@_ARCH850¨
HOST=mvs222
PROTOCOL=2
PORT=1447
SRVR_INSTANCE=ARS850DB
SRVR_INSTANCE_OWNER=ARSSERV2
SRVR_OD_CFG=/etc/ars/V850/ars850.cfg
SRVR_SM_CFG=/etc/ars/V850/ars850.cache
SRVR_FLAGS_SECURITY_EXIT=1
Note that in both the admin and user clients, in the lower right corner is the level of the CMOD SERVER. To get the level of the CMOD CLIENT go to Help -> About OnDemand
Feel free to add any items.
Ed
On the EXEC PGM=ARSSOCKD, the “/” in the parm= line is required to ensure that LE doesn’t try to read CMOD parms and vice versa
XXONMVS222 EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT,MEMLIMIT=NOLIMIT,
XX* PARM='TRACE(ON,15M,,LE=8)/-S -I ARCH1010 -v'
XX* PARM='/-S -I ARCH1010 -v'
XX* PARM=('ENVAR(_CEE_HEAP_MANAGER=CELQMCHK)/-S -I ARCH1010 -v')
XX* PARM='/-S -I ARCH1010 -v -1 /tmp/ela.trc -2 ALL=15'
XX*PARM='/-S -I ARCH1010 -v -d "keystore_location=CKDS,keystore_mkl=*"
XX PARM=('ENVAR(LDAP_DEBUG=2147483647)/-S -I ARCH1010 -v ')
XX* PARM='RPTOPTS(ON)/-S -I ARCH1010 -v'
XX* PARM='DYNDUMP(IBM),RPTOPTS(ON)/-S -I ARCH1010 -v'
XX* PARM='RPTOPTS(ON),RPTSTG(ON)/-S -I ARCH1010 -v'
XX* PARM=('ENVAR(_EDC_DLL_DIAG=TRACE)/-S -I ARCH1010 -v')
On z, if your back end is OAM, it’s so fast you don’t probably don't need cache except for handling the system log (contact L2 if want you an explanation).
You probably don't want to load exclusively to virtual tape. It isn’t fast enough to handle a heavy load of ‘hot’ data.
When defining a test application group, the default number of rows for a table is probably way too large. From the first screen in defining a new app group, select Advanced. On the next screen is the default, 10,000,000 rows, which is probably way too big and a waste of space.
Don’t ever change the permissions on the cache filesystem.
Example of config link to ars.ini file --- need that symlink:
Type Perm Changed-PST8PDT ------Size Filename
_ Dir 755 2021-09-16 09:54 8192 bin
_ Dir 755 2021-04-16 11:27 8192 www
_ Dir 755 2021-04-16 11:23 8192 midserver
_ Dir 755 2021-04-16 11:22 8192 jars
_ Dir 755 2021-04-16 11:22 8192 samples
_ Dir 755 2020-11-25 08:17 8192 locale
_ Dir 755 2020-03-31 11:58 8192 ..
_ Syml 777 2020-02-26 07:49 8 config <------
_ Dir 755 2020-02-26 05:28 8192 .
Ars.ini file has to have a very first line with x’AD’ and x’BD’:
***********************
Ý@SRV@_ARCH850¨
HOST=mvsxxx
PROTOCOL=2
with hex on
Ý@SRV@_ARCH850¨
A7EDE76CDCCFFFB
DC295CD1938850D
That first line is the CMOD instance name, used with arsload. Which is different from the “SERVER_INSTANCE” which refers to the database name
Ý@SRV@_ARCH850¨
HOST=mvs222
PROTOCOL=2
PORT=1447
SRVR_INSTANCE=ARS850DB
SRVR_INSTANCE_OWNER=ARSSERV2
SRVR_OD_CFG=/etc/ars/V850/ars850.cfg
SRVR_SM_CFG=/etc/ars/V850/ars850.cache
SRVR_FLAGS_SECURITY_EXIT=1
Note that in both the admin and user clients, in the lower right corner is the level of the CMOD SERVER. To get the level of the CMOD CLIENT go to Help -> About OnDemand
Feel free to add any items.
Ed