Scheduler configuration

The ports defined for the STC scheduler LISTENER_PORT and range defined by FIRST_PORT through LAST_PORT need to be opened in the firewall protecting the z/OS host system. These ports should not be assigned to the scheduler. Instead, if required, an appropriate RACF profile in the SERVAUTH needs to be defined. Please refer to IBM's TCPIP documentation.

LISTENER_PORT	The IP port that the scheduler listens on for incoming work requests.
FIRST_PORT and LAST_PORT	The port range to be used for user servers. In the sample in Configuring z/Server, 48 user servers can be started simultaneously. Each user server has a different port.
USER_SERVER_JOBNAME	The name of the procedure JCL that the scheduler address space uses to issue a start command for the user server address spaces.

The ports defined for the STC scheduler LISTENER_PORT and range defined by FIRST_PORT:LAST_PORT need to be opened in the firewall protecting the z/OS host system.

Optionally, if you have uncommented MAILHDR in the scheduler procedure, you need to add the MAIL_NOTIFY="1" attribute to the scheduler section. For example:

<STCScheduler
        SCHEDULER_NAME="TAURISPF" LISTENER_PORT="1200" FIRST_PORT="1201"
        LAST_PORT="1249" USER_SERVER_JOBNAME="IVPUSRT" CCSID="037" 
        MAIL_NOTIFY="1"
    >
       <UserServer CCSID="037" />
    </STCScheduler>

For a complete overview of all parameters for a scheduler address space see the parameters listed in Configuration reference that applies to schedulers.

Note:

If you change the name of the STC Scheduler JCL procedure (TAURISPF) in the PROCLIB you must change the SCHEDULER_NAME value to match.
If you change the name of the STC User Server JCL procedure (IVPUSRT) in the PROCLIB you must change the USER_SERVER_JOBNAME value to match.