DTS Error: "TD0C - F/e physical connect error rc = -41" during an attempt to connect to CA IDMS using the CA IDMS ODBC driver (or Type 2 JDBC Driver). What is the underlying cause of this error?

Products

• IDMS
• IDMS - Database
• IDMS - ADS

Issue/Introduction

I'm receiving DTS (-41) errors during an attempt to connect to IDMS using the IDMS ODBC driver (or Type 2 JDBC Driver).
What is the underlying cause of this error?

Environment

Release: IDWINS00100-16.1-IDMS-Server Option
Component:

Resolution

There are a number of possible reasons why this error may occur:

1. One reason is that the CAIENF and the CAICCI subsystem was not started after an IPL of the LPAR.
   
   In the CAIENF joblog check for the following message:

     CAS9626I - CAICCI Subsystem is operational  

1. Another reason is that CAIENF and the CAICCI subsystem was started after the IDMS region brought up.
   
   ENF and CAICCI must be started before an IDMS system (having a cci-line-name   to be ENABLED at startup) may be started. If CAICCI is not running, then you get this error.
   
   One resolution is to vary the cci-line-name  within IDMS. At the Enter Next Task Code, by issuing the command:

     'DCMT VARY LINE cci-line-name   ONLINE'       DC274001 V1700 USER:USERJSM LINE cci-line-name   VARIED ONLINE 

1. Check in Common Services Systems (also known as CA90s); that IDMS system-ID is a known "RESOURCE" within CCI. The command to use is:

                                                     F ENF,DISPLAY,RESOURCES

The response should include the IDMS CV system id (located in the IDMS SYSTEM statement in the SYSGEN).

Check that the Common Services System administrators installed CAIENF from Common Services Systems (CA90s).

 

• Within the IDMS startup job, verify that the cci-line-name   opened successfully with the following message in the IDMS jeslog:

      DC390015 Vxxx OPENING LINE cci-line-name   

and check in the IDMS jes log or OLP for any abends/messages.

 

• The targetIDMSCV may not have been started. Check in SYSVIEW for the IDMS startup job and check if it has been brought up or abended.

 

• The CCITCP address space may not be running or may be listening on a different port from that configured. Check the MVS system console for the following message to indicate that the CCITCP address space has started:

      CAS9850I CAICCI TCP/IP Server Ready PORT xxxxx ADDR xxxxxxxx

• The IDMS central version is not accepting new run units because there are an insufficient number of Pterms. Monitor the number of Pterms and their usage via the command 'DCMT DIS LINE cci-line-name  '.

      DIS LINE cci-line-name                                                        *** Physical Line Display ***                                          PLine-ID cci-line-name                                                              Status InSrv                                                              Module LV                                                                 DDNAME1 SYST1700                                                           LTerm-ID PTerm-ID Type/M Status Term-ID    FES-ID   UCF-Stat UCF-Mode       lterm-id-cci-01 pterm-id-cci-01 BULK   Discon                                             lterm-id-cci-02 pterm-id-cci-02 BULK   Discon                                             lterm-id-cci-03 pterm-id-cci-03 BULK   Discon                                             lterm-id-cci-04 pterm-id-cci-04 BULK   Discon                                             lterm-id-cci-05 pterm-id-cci-05 BULK   Discon                                             lterm-id-cci-06 pterm-id-cci-06 BULK   Discon                                             lterm-id-cci-07 pterm-id-cci-07 BULK   Discon                                             lterm-id-cci-08 pterm-id-cci-08 BULK   Discon                                             lterm-id-cci-09 pterm-id-cci-09 BULK   Discon