Chapter 18. End-to-end scheduling troubleshooting 637
Example 18-47 Excerpt from EQQMLOG
EQQW030I A DISK DATA SET WILL BE FORMATTED, DDNAME = EQQTWSIN
EQQW038I A DISK DATA SET HAS BEEN FORMATTED, DDNAME = EQQTWSIN
EQQG001I SUBTASK E2E RECEIVER HAS STARTED
EQQ3120E END-TO-END TRANSLATOR SERVER PROCESS IS NOT AVAILABLE
EQQW038I A DISK DATA SET HAS BEEN FORMATTED, DDNAME = EQQTWSOU
EQQG001I SUBTASK E2E SENDER HAS STARTED
EQQZ193I END-TO-END TRANSLATOR SERVER PROCESSS NOW IS AVAILABLE
The JESMSGLG of the Controller will also show D37 abends for the files that
require formatting, as shown in Example 18-48.
Example 18-48 Excerpt from JESMSGLG
IEC031I D37-04,IFG0554P,TWSA,TWSA,EQQTWSIN,3595,SBOXB6,TWS.SC63.TWSIN
IEC031I D37-04,IFG0554P,TWSA,TWSA,EQQTWSOU,34CB,SBOXA8,TWS.SC63.TWSOU
If an RC=12 occurs in a CP batch job, check to make sure that the job was not
submitted before the following message is seen in the controller EQQMLOG:
EQQG001I SUBTASK E2E SENDER HAS STARTED
If the batch job was submitted too early, restart the job and check for a successful
completion code.
18.5 OMVS limit problems
Any of several OMVS limit problems can cause end-to-end scheduling
processing to fail. The following console command (output in Example 18-49)
can be used to get a current snapshot of key OMVS values, the high-water marks
for these values, and the limit value as currently implemented:
D OMVS,L
Example 18-49 Output of the D OMVS,L command
BPXO051I 00.06.23 DISPLAY OMVS 412
OMVS 000D ACTIVE OMVS=(01,0A,00)
SYSTEM WIDE LIMITS: LIMMSG=ALL
CURRENT HIGHWATER SYSTEM
USAGE USAGE LIMIT
MAXPROCSYS 38 45 200
MAXUIDS 7 8 50
MAXPTYS 1 2 256
MAXMMAPAREA 0 0 40960
638 IBM Tivoli Workload Scheduler for z/OS Best Practices
MAXSHAREPAGES 308 1934 131072
IPCMSGNIDS 0 0 500
IPCSEMNIDS 4 4 500
IPCSHMNIDS 0 0 500
IPCSHMSPAGES 0 0 262144
IPCMSGQBYTES --- 0 262144
IPCMSGQMNUM --- 0 10000
IPCSHMMPAGES --- 0 256
SHRLIBRGNSIZE 0 0 67108864
The next sections illustrate the effect of having the values for MAXFILEPROC,
MAXPROCSYS, and MAXUIDS set too low.
18.5.1 MAXFILEPROC value set too low
To test the effect of having MAXFILEPROC set too low, we issued this command:
SETOMVS MAXFILEPROC=5
Note that the normal value on the system used for the test was 2000, which is set
in the BPXPRMxx member in the system PARMLIB. The current value of
MAXFILEPROC is also displayed if the following command is issued:
D OMVS,O
With MAXFILEPROC=5 in effect, the E2E Server was started, and the messages
shown in Example 18-50 were seen in the EQQMLOG.
Example 18-50 Excerpt from EQQMLOG
EQQPH33I THE END-TO-END PROCESSES HAVE BEEN STARTED
EQQZ024I Initializing wait parameters
EQQPH07E THE SERVER STARTER PROCESS ABENDED.
EQQPH07I THE STARTER PROCESS WAS CREATED TO PROCESS E2E REQUESTS
The TWSMERGE log in USS stdlist had the following message for the domain
manager (HR82 in this example) and the FTAs:
MAILMAN:+ AWSBCV027I Unlinking from HR82
After correcting the MAXFILEPROC value with the following command and
cycling the E2E Server, the problem was corrected:
SETOMVS MAXFILEPROC=2000
The conclusion is that if message EQQPH07E is seen in the server EQQMLOG,
the value of MAXFILEPROC should be checked and increased if needed.
Chapter 18. End-to-end scheduling troubleshooting 639
18.5.2 MAXPROCSYS value set too low
We tested a small value for MAXPROCSYS in a similar manner to the way
MAXFILEPROC was tested in the previous section. The current value for
MAXPROCSYS can be seen with either the D OMVS,L command or the D OMVS,O
command. We issued the following command to set a small value for
MAXPROCSYS:
setomvs maxprocsys=5
After this, the E2E Server task was started. The messages shown in
Example 18-51 appeared in the server EQQMLOG.
Example 18-51 Excerpt from EQQMLOG
EQQZ005I OPC SUBTASK SERVER IS BEING STARTED
EQQPH09I THE SERVER IS USING THE TCP/IP PROTOCOL
EQQPH18E COMMUNICATION FAILED,
EQQPH18I THE SOCKET SOCKET CALL FAILED WITH ERROR CODE 156
EQQPH08I TCP/IP IS EITHER INACTIVE OR NOT READY
EQQPH08I CHECK THAT TCP/IP IS AVAILABLE
EQQPH00I SERVER TASK HAS STARTED
EQQPH18E COMMUNICATION FAILED,
EQQPH18I THE SOCKET SOCKET CALL FAILED WITH ERROR CODE 156
EQQPH08I TCP/IP IS EITHER INACTIVE OR NOT READY
EQQPH08I CHECK THAT TCP/IP IS AVAILABLE
EQQPH35E CANNOT START STARTER PROCESS:
EQQPH35I BPX1ATX FAILED WITH RC=0156, RSN=0B0F0028
We used the TSO BPXMTEXT command to check the meaning of the reason
code shown in the EQQPH35I message (0B0F0028):
TSO BPXMTEXT 0B0F0028
The information shown in Example 18-52 was displayed by BPXMTEXT.
Example 18-52 Output of the TSO BPXMTEXT 0B0F0028 command
JRMaxProc: The maximum number of processes was exceeded
Action: Retry after some processes have ended, or change the maximum
number of processes allowed.
To correct the problem, MAXPROCSYS was reset to its normal value with this
command, and the E2E Server was stopped and started again:
setomvs maxprocsys=200

Get IBM Tivoli Workload Scheduler for z/OS Best Practices: End-to-end and mainframe scheduling, 2nd Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.