Hi Ed.
Fortunately, we figured out the root cause. The DB2 loadlib and DBRMLIB were out-of-sync. In prior DB2 maintanence upgrades, we would get a -805 for package DSNCLIC1 and cc=6, and we know to rebind the DSNACLI packages. In this case, we only got the cc=6. After tracing our steps, figured out that our runtime dbrmlib and smpe db2 dbrmlib were out-of-sync with changes in DSN@LIF4 member. After rebinding with the smpe dbrmlib, ARSSOCKD successfully started and its operational.
Thanks for your help on the issue and with setting an ODBC trace. I'll put this in my toolbox.
Regards,
Ray Mamaradlo
Answers to questions
Ondemand 8.5.0.6
D OMVS,O
RESPONSE=A0
BPXO043I 09.12.27 DISPLAY OMVS 505
OMVS 0011 ACTIVE OMVS=(00,A0)
CURRENT UNIX CONFIGURATION SETTINGS:
MAXPROCSYS = 5000 MAXPROCUSER = 200
MAXFILEPROC = 64000 MAXFILESIZE = NOLIMIT
MAXCPUTIME = 1000 MAXUIDS = 300
MAXPTYS = 800 MAXIOBUFUSER = 2048
MAXMMAPAREA = 40960 MAXASSIZE = 41943040
MAXTHREADS = 10000 MAXTHREADTASKS = 5000
MAXCORESIZE = 4194304 MAXSHAREPAGES = 10000000
IPCMSGQBYTES = 1048576 IPCMSGQMNUM = 20000
IPCMSGNIDS = 20000 IPCSEMNIDS = 20000
IPCSEMNOPS = 32767 IPCSEMNSEMS = 32767
IPCSHMMPAGES = 25600 IPCSHMNIDS = 500
IPCSHMNSEGS = 100 IPCSHMSPAGES = 2621440
SUPERUSER = BPXROOT FORKCOPY = COPY
STEPLIBLIST =
USERIDALIASTABLE=
PRIORITYPG VALUES: NONE
PRIORITYGOAL VALUES: NONE
MAXQUEUEDSIGS = 1000 SHRLIBRGNSIZE = 67108864
SHRLIBMAXPAGES = 4096 VERSION = RESA04
SYSCALL COUNTS = NO TTYGROUP = TTY
SYSPLEX = YES BRLM SERVER = N/A
LIMMSG = NONE AUTOCVT = OFF
RESOLVER PROC = RESOLVER LOSTMSG = ON
AUTHPGMLIST = NONE
SWA = BELOW NONEMPTYMOUNTPT = WARN
SERV_LINKLIB =
SERV_LPALIB =
ALTROOT =
MAXUSERMOUNTSYS = 30 MAXUSERMOUNTUSER= 3
MAXPIPEUSER = 8730 PWT = ENV
UMASK = NONE