The SVDBSPR job stream shown below initiates a Mainframe Server component. To modify the Mainframe startup parameters include SYSIN or SYSIPT data in the job stream. CA Datacom Server reads the SYSIN/SYSIPT data during Mainframe Server initialization and echoes it to the SYSPRINT/SYSLST file.
Example: z/OS Startup JCL
//DBSERVER EXEC PGM=SVDBSPR,REGION=6000K //STEPLIB DD DSN= (See the Prepare Your JCL topic) //CAOESTOP DD DUMMY //CEEOPTS DD DSN=xxxx.CAYTMAC(CEEUOPT),DISP=SHR //SYSTCPD DD DSN=VTAM.TCPIP.TCPIP.DATA,DISP=SHR //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SNAPER DD SYSOUT=* //BATCHOUT DD SYSOUT=* //TCPTRACE DD SYSOUT=* //SYSIN DD * SERVERNAME=TCP_DEV_xxxx APPLID=TCP_DEV_xxxx PLANNAME=$MBH AUTHID=SYSUSR PROTOCOL=BOTH DBUSERS=n //
Note: CEEOPTS should point to the CEEUOPT delivered in PTF RO52452. This ensures that the use of TCP/IP is optimized. For a standalone installation of CA Datacom Server, CEEUOPT is delivered to the CAYTMAC library. For CA Datacom Server delivered as a component of CA Datacom/AD, CEEUOPT is delivered to the CAAXMAC library, so the //CEEOPTS DD statement above should reflect CAAXMAC instead of CAYTMAC.
If tracing is enabled, additional output files for TCP trace activity is dynamically allocated as TCPTRACE and T4Annnnn, where nnnnn is a sequential number. DD statements for these files are not required.
You can submit multiple instances of this job stream for each Mainframe Server component your site requires. The STEPLIB/JOBLIB determines the Multi-User Facility in which the Mainframe Server component operates. Startup parameters uniquely identify each Mainframe Server as explained later.
Complete details about the SQL plan options are in the CA Datacom/DB SQL User Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|