About this task
The ARSSOCKD procedure is used to start the server as a started task.
A sample ARSSOCKD procedure is provided in the SARSINST library. You must customize the procedure for your environment and copy the customized procedure into the PROCLIB concatenation.
The
following is the sample ARSSOCKD procedure.
Figure 1. Sample ARSSOCKD procedure.
//ARSSOCKD PROC
//ARSSOCKD EXEC PGM=ARSSOCKD,REGION=0M,TIME=NOLIMIT
//STEPLIB DD DISP=SHR,DSN=ARS.V9R5M0.SARSLOAD
// DD DISP=SHR,DSN=DB2.V10R1M0.SDSNEXIT
// DD DISP=SHR,DSN=DB2.V10R1M0.SDSNLOAD
//*DSNAOINI DD PATH='/usr/lpp/ars/V9R5M0/config/cli.ini'
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*The following list explains the statements highlighted
in Figure 1:
- //STEPLIB DD
- Specifies the program libraries, which must be customized for the local naming conventions.
- //*DSNAOINI DD
- Specifies the location and name of the ODBC parameter file. This
DD statement must be un-commented and customized if you need to configure
ODBC. For more information about configuring ODBC, see the DB2® V10 for z/OS® ODBC Guide and Reference.
Note: Environment variables may be specified by
using the ENVAR Language Environment runtime option
on the PARM= JCL keyword. See z/OS Language
Environment Programming Reference for more information. For
example, to set the locale (and the associated code page) for the
server, you could specify: PARM='ENVAR("LC_ALL=De_DE.IBM-273")/'
If you wish to specify more environment variables than will fit in the 100-character PARM= keyword, additional environment variables can be set from an MVS™ data set or HFS file by using the _CEE_ENVFILE environment variable. See z/OS XL C/C++ Programming Guide for details about the _CEE_ENVFILE environment variable. Note that for an MVS data set, the data set must be allocated with RECFM=V or RECFM=VB.