search cancel

How to alter/remove the SYSTCPD DD from JCL for CA Mainframe Connector for Linux

book

Article ID: 133839

calendar_today

Updated On:

Products

COMMON SERVICES FOR Z/OS Common Services MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME SOLVE:Access Session Management

Issue/Introduction

Currently running a CA Mainframe Connector for Linux on System z  task on an LPAR. Currently the JCL for this task contains a SYSTCPD DD statement. The network uses a RESOLVER task to handle the SYSTCPD data set allocation. The LNXCONA task is one of the last tasks to contain a SYSTCPD DD statement on this sysplex.

  • When trying to run without the SYSTCPD DD, the following occurred:

     LXIN0012 Invalid data set allocated to SYSTCPD: N16C01 DDNAME NOT FOUND, DD=SYSTCPD

  • When an attempt was made to define SYSTCPD DD DUMMY,  the following was returned:

     LXIN0012 Invalid data set allocated to SYSTCPD: data set not physical sequential

In each situation the LNXCONA task shutdown.

Explain how to alter/remove the SYSTCPD DD to allow the RESOLVER task to handle the TCPIP stack.

 

Environment

OS: z/OS
Component : CA MAINFRAME CONNECTOR FOR LINUX ON SYSTEM Z

Resolution

Change the stack connection type from a STACKTYPE of IBM to a StackType of USS - This is a configuration parm for the Linux connect address space.


USS does not use the SYSTCPD, and hence a stack configured to use USS connections can remove the requirement to code the SYSTCPD DD in the JCL.