If the holder has successfully started it will also have started your scheduler. You can now verify that the scheduler has started correctly.
In addition to the regular JESx DD statements and SYSTSPRT/ZCOTSPRT, the job log of a running scheduler address space should contain the following DD names:
| DD Name | Function |
|---|---|
| MAINTASK | (LE) Messages from MAINTASK. |
| LISTENER | (LE) Listener for client requests. |
| CMDTASK | (LE) Messages from CMDTASK; contains command output. |
| SRVTASK | (LE) Messages from SRVTASK. |
| MSGTASK | (LE) Task to queue messages to a USS message queue. |
| T000000x, x=1..NUMTCB | (LE) Messages from T000000x, the worker tasks. |
| MAILBOX | If email notification is configured. |
A number of messages reference these DD statements as "LE message files".
A scheduler address space has started successfully when the hardcopy log shows:
+TAU0067I zServer startup completed for TAURISPF for JESx and ASID nnnn
To verify that the scheduler is responding to work requests you can customize and submit the verification job hlq.ZSERVER.JCL(IVPVERI):
//TAURHLQ SET TAURHLQ=hlq.ZSERVER //JOBLIB DD DISP=SHR,DSN=&TAURHLQ..LOADLIB //*-----------------------------------------------------------------* //*- Install Verification Job -* //*- -* //*- Valid Selects -* //*- =========================================================== -* //*- 1 EXEC REXX IVPREXXE (echo rexx) -* //*-----------------------------------------------------------------* //TAURIVP EXEC PGM=TAURIVP //SYSPRINT DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSOUT DD SYSOUT=* //SYSIN DD * IVP_SELECT = 1 IVP_Server = 'nnn.nnn.nnn.nnn' IVP_Port = 1200; IVP_COMPAT = 2 IVP_IPNAME = 'TCPIP' ; /*
The IVPVERI output should look like this:
IVP0002I Selection code for IVP was : 1
EXEC IVPREXXI (echo REXX)
IVP0003I call to zServer ended with RC : 0
===================================================================
Answer from zServer is 203 Bytes long.
===================================================================
00000000 000000CB 4CD4E2C7 40C6C1C3 C9C47E7F * <MSG FACID="*
00000010 D3C9C37F 40D4E2C7 D5D67E7F F0F0F1F0 *LIC" MSGNO="0010*
00000020 7F40E2C5 E5C5D9C9 E3E87E7F C57F6E40 *" SEVERITY="E"> *
00000030 F0F97AF4 F87AF3F7 4BF0F8F9 40D38983 *09:48:37.089 Lic*
00000040 85958385 40A58996 9381A389 96957A40 *ence violation: *
00000050 E38889A2 40A28599 A5859940 83819540 *This server can *
00000060 969593A8 40828540 A4A28584 40A38899 *only be used thr*
00000070 96A48788 40819540 E3C1E4D9 E4E24083 *ough a licenced *
00000080 93898595 A34B4040 40404040 40404040 *client. *
00000090 40404040 40404040 40404040 40404040 * *
000000A0 40404040 40404040 40404040 40404040 * *
000000B0 40404040 40404040 40404040 40404040 * *
000000C0 40404040 404C61D4 E2C76E00 00000000 * </MSG> *
If you receive a return code of 49 in message IVP0003I, check if numbering was inadvertently turned on in the member from which this job was submitted. If it was, turn off numbering.
Make sure that this job is run for both the STC scheduler and the CEA scheduler (if one is configured).