CSSMTP implements a compatibility test mode, which allows
you to test CSSMTP in your production environment without disrupting
your existing mail workloads.
Procedure
To implement the CSSMTP compatibility test, perform the
following steps:
- Configure EZBMCOPY to run as JES writer SMTPD and to allocate
copies of the spool files it creates to writers SMTPD1 and CSSMTP. See the example JCL below about how to configure EZBMCOPY:
//EZBMCOPY PROC
//STEP EXEC PGM=EZBMCOPY,PARM='WRITER=SMTPD'
//OUT1 OUTPUT WRITER=SMTPD1
//OUT2 OUTPUT WRITER=CSSMTP
//STEPLIB DD DSN=JES2.TESTING.LOAD,DISP=SHR
//SYSUT2 DD SYSOUT=*,SPIN=UNALLOC,OUTPUT=(*.OUT1,*.OUT2),HOLD=NO
//SYSPRINT DD SYSOUT=*
//SYSIN DD DUMMY
Note: The writer names in this procedure
are examples based on
Figure 1.
- Start CSSMTP in test mode with the JES writer name CSSMTP.
See OPTIONS TESTMODE configuration statement for
more information.
- Change SMTPD's job name to SMTPD1.
Tip: SMTPD writer name is the same as SMTPD job
name. Therefore, if you have any port reservation statements for the
SMTPD job name in the TCP/IP profile, update the statements by specifying
the new job name after you change the job name. Also, if you did not
specify the MAILFILEDSPREFIX parameter in the SMTPD configuration
file, the default value of the parameter changes to the new job name.
- Start EZBMCOPY.
Results
Because EZBMCOPY makes two copies of mail spool files, spool
usage increases during the compatibility tests.