Abend S019 when trying to sign on to a new IDMS CV using UCF

Products

• IDMS

Issue/Introduction

When signing on to a CV that has been newly created or upgraded, it is possible to get an S019 abend.

Environment

Release: All supported releases.

Cause

One cause for the S019 error is an authorization or security error when attempting to sign on through UCF. Check the IDMS CV LOG for the corresponding security violation message.

Resolution

If a CV is brought up with a different RHDCSRTT security table than the one which was used in testing, this S019 can easily result. It is important to verify that the CV is using an RHDCSRTT module which has been tested and is valid. 

An S019 can also occur when a CV has been upgraded to 18.0 or later and the USRIDXIT has not been re-linked appropriately. As of 18.0 the methodology for that has changed: as of 18.0: USRIDXIT must be included in the link-edit of IDMSUXIT, and no longer with IDMSSTRT (as in 17.0). 

If that has not been done, here are the steps to do the relink:

1. Set up the exit using an USRIDXIT. Here the default userid is set to be "Z000020".
   
   DFLTUSER DC CL18'Z000020'


2. Compile and link-edit the exit into your CUSTOM.LOADLIB and include it in the link-edit of IDMSUXIT as follows.
    
   ORDER IDMSUXIT 
INCLUDE CAGJLOAD(IDMSUXIT) <-- the module as delivered during install 
INCLUDE CUSTLIB(USRIDXIT) <-- my own useridxit 
ENTRY UEXITS 
SETOPT PARM(REUS=NONE) 
NAME IDMSUXIT(R) 
   
   and save the module in the CUSTOM.LOADLIB too.
   
   
3. With r18.5 PTF RO60928 (fixed-in-source in r19.0), IDMS will load IDMSUXIT from STEPLIB if it's found in there, and because of that, it may be necessary to add the CUSTOM.LOADLIB in front of CAGJLOAD in the STEPLIB concatenation of your startup JCL.
   Note: if WTOEXIT/WTOREXIT contain IDENTIFY calls then:
   
   a) both MUST be linked into the IDMSUXIT 
   b) removed from the startup PARMs 
   c) the library containing IDMSUXIT MUST be defined in STEPLIB

After successfully completing the above steps to relink the USRIDXIT, test to see if a signon is successful by starting the CV, then running the DCPROFIL task. If everything is OK, the * Named User Exits * screen on DCPROFIL should show something like the following: 

                           * Named User Exits * 

EXIT                ENTRY           EXIT                ENTRY 
NAME       DEFINED  POINT           NAME       DEFINED  POINT 
BTCIDXIT   NO       00000000        DBLUEREX   NO       00000000 
IDDEXITB   NO       00000000        IDDEXITO   NO       00000000 
IDMSAJNX   NO       00000000        IDMSCLCX   NO       00000000 
IDMSDPLX   NO       00000000        IDMSIOXT   NO       00000000 
IDMSIOX2   NO       00000000        IDMSJNL2   NO       00000000 
SCHEXITB   NO       00000000        SCHEXITO   NO       00000000 
SGNEXITB   NO       00000000        SGNEXITO   NO       00000000 
SUBEXITB   NO       00000000        SUBEXITO   NO       00000000 
TCKREXIT   NO       00000000        USRIDXIT   YES      3A601108 <<<<<<<--------- 
WAITEXIT   NO       00000000        WTOEXIT    YES      00028250 
WTOREXIT   NO       00000000 

The list will probably be different, but it should show the USRIDXIT in the list somewhere. 

Finally, after connecting to the system, run a DCUF SHOW USER ALL command and it should show the userid used to log on: 

SHO USER ALL 
*USER ID         PRI  *LTERMID
USER001          000  LTVTM001
Z000020          000  UCFLT01

Additional Information

Another potential cause of an S019 abend: Message BACK END SYSTEM IS NOT ACTIVE in UCFTSO clist.