Author Topic: Shutting down arssockd  (Read 83 times)


  • Jr. Member
  • **
  • Posts: 59
    • View Profile
Shutting down arssockd
« on: November 22, 2020, 11:16:11 AM »
   We upgraded to version a few months ago and this weekend we had to shutdown arssockd so the servers could be patched.

We logged in as root and switced user to ARCHIVE but were not able to shutdown arssockd via the arssockd stop or the arssockd -T commands

We ended up having to kill the arssockd process.  We do not have the issue in CERT where we are at instead of

I thought maybe the newest fixpack addressed the issue but after looking at the README I did not see any reference to it.

  Has anyone else experienced issues where the arssockd stop command does not shutdown CMOD ?

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 1964
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Shutting down arssockd
« Reply #1 on: November 22, 2020, 03:32:52 PM »
If it doesn't shut down gracefully, it's okay to kill it.  Just do what you can to shut down cleanly - no loads, no admin users making changes, no arsmaint running, etc.

IBM CMOD Professional Services:
Call:  +1-866-533-7742  or  eMail:
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR


  • Hero Member
  • *****
  • Posts: 1007
    • View Profile
Re: Shutting down arssockd
« Reply #2 on: November 23, 2020, 11:27:26 AM »
Just for completeness - I don't think this affects anybody other than z.

There's a fairly new PTF for a shutdown issue on z.


++PTF(UI70688)    /* 5655-H3900-H272A10 */.                           
++VER(P115) FMID(H272A10) PRE(UI65845) SUP(AH26134)                   
 PROBLEM DESCRIPTION(S):                                             
    PH26134 -                                                         
      ARSSOCKD LOOP AT SHUTDOWN.                                     
      PROBLEM SUMMARY:                                               
      * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *
      *                 and above.                                   *
      * PROBLEM DESCRIPTION: After issuing the STOP ARSSOCKD         *
      *                      command, the server goes into a loop    *
      *                      consuming CPU.  An IPCS SYSTRACE will   *
      *                      show the looping TCB is in              *
      *                      ArcZ31OSP_Destruct.                     *