action.skip

Start the DCAS Server

The DCAS server can be started as a generic server without stack affinity or as a server with affinity to a specific TCP/IP stack. The DCAS server can be started in different ways (detailed steps follow):

  • automatically when the TCP/IP address space is started
  • from the z/OS UNIX shell
  • from an MVS started procedure

To start the DCAS server automatically when the TCP/IP address space is started

Specify DCAS on the AUTOLOG statement in the TCPIP profile dataset. For example: 

AUTOLOG 
DCAS 
ENDAUTOLOG
The following sample procedure can be used to start DCAS. First, enter the command S DCAS. To pass optional parameters to DCAS, specify them after the final slash (/) on the PARM statement, for example: 

// PARM=('POSIX(ON) ALL31(ON)' 
// 'ENVAR("LIBPATH=/usr/lib")/-d 3 -l SYSLOGD')

Sample procedure

//DCAS PROC 
//* DEBUGGING AND LOGGING MAY BE REQUIRED TO HELP DETERMINE A PROBLEM 
//* THE DCAS. 
//* 
//* -D OR -D - INDICATES DEBUGGING LEVEL REQUESTED. 
//* FORMAT: -D LEVEL 
//* LEVEL IS: 1=LOG ERROR AND WARNING MESSAGES 
//* 2=LOG ERROR, WARNING, AND INFO 
//* 3=LOG ERROR,WARNING, INFORMATI 
//* 
//*<BR>//DCAS EXECPGM=EZADCDMN,REGION=4096K,TIME=NOLIMIT, 
// PARM='POSIX(ON) ALL31(ON) / -d 3 -l SYSLOGD' 
//* 
//SYDENV DD DUMMY 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD DUMMY 
//SYSERR DD SYSOUT=* 
//SYSOUT DD SYSOUT=* 
//CEEDUMP DD SYSOUT=* 
//*

You will find a sample start procedure in EZADCASP in the SEZAINST dataset.

To start the DCAS server from the z/OS UNIX shell

Use the following format:

dcas <parameter_1> <parameter_2> <parameter_3> &

To start the DCAS server from an MVS started procedure

Use the following format:

PARM=.../<parameter_1> <parameter_2> <parameter_3>

Optional parameters

The following optional parameters can be used from either the z/OS UNIX shell or the MVS started procedure:

-d or -D

Indicates debugging. The following levels apply:

  • 1= Specifies log error and warning messages.
  • 2= Specifies log error, warning, and informational messages.
  • 3= Specifies log error, warning, informational, and debug messages. This is the default.

-l or -L

Indicates logging to SYSLOGD or to a designated log file. If you do not specify this parameter, logging defaults to /tmp/dcas.log. If you specify a debug level, but not logging, then the DCAS server attempts to open the default log file /tmp/dcas.log. If this fails, debugging is turned off. For SYSLOGD, the DCAS server uses the log facility local0.

-c or -C

Indicates the requested configuration file (for example, /u/userx/passtick.conf). If you do not specify this parameter, the DCAS server looks for the configuration file using the following search order: DCAS_CONFIG_FILE environment variable /etc/dcas.conf tsouserid.DCAS.CONF TCPIP.DCAS.CONF

If the DCAS server does not find a valid configuration file, it will not start.

When DCAS is started, the process ID (pid) is stored in a Hierarchical File System (HFS) file. The file name under which it is stored depends upon how you configure DCAS:

  • If the DCAS server is configured with TCP/IP stack affinity, the pid file is named /tmp/dcas.tcpipname.pid where tcpipname is the name of the TCP/IP stack for which DCAS has affinity.
  • If the DCAS server is configured without stack affinity, the pid file is named /tmp/dcas.INET.pid.

You can stop the DCAS server from the UNIX shell or from MVS:

  • To stop the DCAS server from the UNIX shell, use the following command: kill -s SIGTERM pid
  • To stop the DCAS server from MVS, use the following command: P DCAS