Uninstalling CONNX for Adabas Components
The CONNX for Adabas TCP/IP Server Setup client application transfers the CONNX components to the target OS/390 / z/OS host via TCP FTP. After the initial FTP step, the CONNX installation continues via a batch job submission using TSO ISPF. Final optional installation steps for the CONNX for Adabas Started Task components include manual additions of a JCL procedure (CNXADA) and a REXX exec file (CNXSTOP) to the system PROCLIB and SYSPROC partitioned data sets.
Given a default CONNX installation prefix of CONNX.ADABAS, the CONNX for Adabas Started Task installation JCL partitioned data set is CONNX.ADABAS.CNTL. Member REMOVE contains batch uninstallation JCL.
To uninstall the CONNX for Adabas Started Task components:
1. Before submitting the uninstallation JCL, find and stop all instances of the CONNX for Adabas Started Task/Batch Job TCP/IP Listener program CNXRUNA. For example, batch job CNXADAJ is executing, listening on TCP/IP port 6789.
2. Use the TSO NETSTAT command to list the TCP/IP listen port dedicated to CNXADAJ, and all active client/server connections:
EZZ2587I CNXADAJ 0009C426 123.123.123.123..1927 123.123.123.124..4397
Establsh
EZZ2587I CNXADAJ 0009C424 0.0.0.0..6789 0.0.0.0..0
Listen
EZZ2587I CNXADAJ 0009C42D 123.123.123.123..1930 123.123.123.125..4405
Establsh
EZZ2587I CNXADAJ 0009C429 123.123.123.123..1928 123.123.123.126..4401
Establsh
EZZ2587I CNXADAJ 0009C42B 123.123.123.123..1929 123.123.123.127..4403
Establsh
3. Use the TSO CNXSTOP command, specifying port 6789, to terminate the CNXRUNA listener program and its active subtasks.
4. Repeat these steps for other any other batch jobs/started tasks which are currently executing the CONNX TCP/IP listener program CNXRUNA.
5. After stopping all instances of the CNXADA Started Task(s)/Batch Job(s), you can submit the JCL in member REMOVE. Note that the last control record of the IDCAMS DELETE step references the CONNX.ADABAS.CNTL partitioned data set, so be sure to submit the job and deallocate the partitioned data set from your TSO session by navigating to another ISPF option.
6. Also note that the second IDCAMS DELETE step for the CONNX.ADABAS.LOAD partitioned data set is commented out. This is by design, in case the CONNX Started Task/Batch job load modules were linked into an existing load library. It is recommended, but not required, to install CONNX into a separate load library.
7. The IDCAMS DELETE steps should return zeroes for all data sets which are not allocated to another batch job, started task, or TSO session. For data sets which do not exist or are allocated to other jobs or tasks, the IDCAMS return code is 8. The undeleted data sets, if any, can be deleted via ISPF or via a second run of the REMOVE JCL after the dataset sharing conflicts have been resolved.
To verify that all CONNX for Adabas components have been uninstalled, use ISPF option 3.4 to list and delete the datasets defined with the (default) CONNX.ADABAS high-level qualifier. Next, delete all versions of the CNXADA procedures from the production JCL PROCLIB. Finally, if the CNXSTOP REXX exec file has been copied to a SYSPROC PDS such as SYS1.LOCAL.CLIST, delete the CNXSTOP member.