Uninstalling the CONNX for VSAM Started Task Components
1. Before submitting the uninstallation JCL, find and stop all instances of the CONNX for VSAM Started Task/Batch Job TCP/IP Listener program CNXRUNB.
2. The TCP/IP ports dedicated to these jobs can be found via the TSO NETSTAT command.
3. Execute the CNXCFG REXX command file using either the implicit or the verbose syntax below, and repeat the command for all the ports.
From the ISPF Command Shell:
cnxcfg p(stop port-number)
or
exec 'connx.stask.cntl(cnxcfg)' 'p(stop port-number)'
From any ISPF Command line:
tso cnxcfg p(stop port-number)
or
tso exec 'connx.v08r09.stask.cntl(cnxcfg)' 'p(stop port-number)'
Repeat this process for each instance of the CNXVSAM/CNXSCT Started Task(s)/Batch Job(s).
4. After stopping all instances of the CNXVSAM / CNXVSCT Started Task(s)/Batch Job(s), you can submit the JCL in member @REMOVE or @REMOV01. The last control record of the IDCAMS DELETE step references the CONNX.STASK.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:
The second IDCAMS DELETE step for the CONNX.STASK.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. If the CONNX load modules were installed into a new load library:
Step 2 can be then commented in.
5. 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 tasks, the IDCAMS return code will be 8. The undeleted data sets, if any, can be deleted via ISPF or via a second run of the @REMOVE or @REMOV01 JCL after the data set sharing conflicts have been resolved.
To verify that all CONNX for VSAM Started Task components have been uninstalled, you can use ISPF option 3.4 to list and delete the data sets defined with the (default) CONNX.STASK high-level qualifier. Next, delete all versions of the CNXVSAM/CNXVSCT procedures from the production JCL PROCLIB. Finally, if the CNXCFG REXX exec file has been copied to a SYSPROC PDS such as SYS1.LOCAL.CLIST, delete the CNXCFG member.