Mainview AutoOPERATOR: How to fix DX0954E, DX0951E error in the PAS after setting ALLOWUSERKEYCSA(NO) dynamically?

Version 2
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView AutoOPERATOR


    APPLIES TO:

    MainView AutoOPERATOR all supported versions



    QUESTION:

    When I changed VSM ALLOWUSERKEYCSA(YES) to VSM ALLOWUSERKEYCSA(NO) via the DIAGnn member of SYS1.PARMLIB and issued SET DIAG command, I saw a load of DX0954E messages in the SYSLOG:

    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    00000090 DX0954E BBI/DXAUTX ABEND DETECTED IN SSI ROUTINES FOR SSID=SSA4
    ... ...

    followed by:
    *DX0951E BBI/DXAUTX TERMINATED, COLD START REQUIRED FOR SSID=SSA4
    DM0903E BBI/DM STAE EXIT ENTERED DURING WTO PROCESSING- UNABLE TO ISSUE WTO


    How to fix these errors?


    ANSWER:

     

      Dynamically modifying ALLOWUSERKEYCSA in SYS1.PARMLIB(DIAGxx) from YES to NO or NO to YES, will result in the BBI-SS PAS to fail to restart or may cause other failures in processing. The BBI-SS PAS does not support  dynamic alteration of this setting. If dynamically altered, various errors may occur including the inability to restart the PAS. Error messages such as the following may be seen: 
      
                                                  
      
      SS4007E EXISTING SSD KEY (4) DOES NOT MATCH STARTUP EXECUTION KEY
      
                                                                      
      
      The solution is to stop the PAS and while still using the original  ALLOWUSERKEYCSA setting as when the PAS was first started, issue another START command for the PAS with the START=FREE option. This option will start the PAS, some common storage will be FREEMAINed, and then the PAS will stop. After that completes you can change the ALLOWUSERKEYCSA setting and then restart the PAS as normal. This will default to a COLD START.    
      
                                                                                
      
      For each dynamic change of ALLOWUSERKEYCSA, the following steps should be taken:   
      
                                                                       
      
      1. Before changing ALLOWUSERKEYCSA, stop the PAS                           
      
      2. Then start the PAS with START=FREE                                     
      
      3. Change ALLOWUSERKEYCSA to the desired setting                          
      
      4. Restart the PAS. 
      
    Running the BBI-SS PAS in KEY4 is highly recommended as it provides a higher level of security for common storage. 

    If you want to change the BBI-SS PAS to use KEY4, but still want to use ALLOWUSERKEYCSA(YES), then you can change the BBI-SS PAS JCL to execute SSLOAD4 program instead of SSLOAD.  

    When ALLOWUSERKEYCSA(NO) is used, it does not matter if PGM=SSLOAD or PGM=SSLOAD4 is coded in the BBI-SS PAS JCL, KEY 4 storage will be allocated.

     


    Article Number:

    000167282


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles