HCL Workload Automation, Version 9.4

Troubleshooting

To assist in troubleshooting, ensure that the JES log is obtained for the EEWSPACE and EEWSERVE started tasks. This helps in determining the context in which a message was issued. Depending on the job scheduling interface you use, additional helpful information might be obtained from other logs.

EEWI27I APPLICATION application WAS INSERTED IN CP WITH INPUT
ARRIVAL DATE AND TIME yymmddhhss

EEWI28W yymmdd hhmmss APPLICATION appl WAS NOT INSERTED IN
 CURRENT PLAN WITH INPUT ARRIVAL DATE AND TIME iadatetime

EEWI29I yymmdd hhmmss TASK task MODULE module ISSUED, MACRO macro NEAR LABEL label
 WITH RETURN CODE = code AND ERROR NUMBER = err

EEWI30S yymmdd hhmmss module CA7SPAN MUST BE 4 DIGITS IN FORMAT HHMM

EEWI31E TASK task MODULE module LAUNCH OF JOB 'jobname' FAILED

EEWI32S yymmdd hhmmss module AT LEAST ONE INTERFACE MUST BE DIFFERENT FROM NO

EEWI33W yymmdd hhmmss TASK task APPLICATION application NOT FOUND

EEWI34W APPLICATION application NOT FOUND

EEWI35W JCL dataset(member) NOT FOUND

EEWI36W yymmdd hhmmss IA and IATIME cannot be specified together

EEWI37W yymmdd hhmmss DEADLINE and DEADLINETIME cannot be specified together

EEWI38I jobname(jobid) nl n2 result (restype)

n1 indicates the number of seconds passed from the request
n2 indicates the number of seconds of CPU time consumed
result can assume one of the following values:
ABEND

If the job abends. In this case restype can be:
Sxyz

In case of System Abend

Unnnn

in case of User Abend

CONDCOD

If the job does not end successfully due to the condition code of one step that does not match the definition. In this case restype contains: the RC=nnnnn value of the return code of the last step that has been run, if LASTSTEP specified, or of the worst step that does not match the definition of the job on the distributed side.

EXEC

If the job is running or is in the input queue.

JCLERRO

If the job failed due to a JCL error.

SUCCES

If the job completed successfully.

UNKNOWN

If the jobid is unknown

blank

In case of an internetwork dependency when the manual submission was not performed.

Note: All the above messages are written in the EEWSPACE or in the EEWSERVE log files. These are the files indicated in the SYSTSPRT DD card of the respective procedure. In the files the messages are written starting from column 1, except for the messages that do not contain the date and time after the message identifier, for example EEWI27I. These messages appear with different characteristics in the z/OS® system and in HCL Workload Automation. In the z/OS system log the messages appear in the text of another message and in some cases they might appear truncated. This is because the maximum length of each text record is limited to 251 characters. In HCL Workload Automation they are always displayed in their complete form.

The module names are:

Module Name	Description
EEWPRE84	Previous SMF exit
EEWTCP00	Main processing routine
EEWTCP01	Server test vehicle
EEWTCP02	Main dataspace construction routine
EEWTCP05	Establish ESTAE routine to issue failure message
EEWTCP07	Find data set name associated with open ACB/DCB
EEWTCP08	Find data set name associated with DDNAME
EEWTCP10	Initialize and examine variables
EEWTCP15	Locate and initialize control blocks
EEWTCP20	Locate and initialize control blocks
EEWTCP21	Client test vehicle
EEWTCP22	Client test vehicle
EEWTCP23	Client test vehicle
EEWTCP25	Concurrent server
EEWTCP26	Concurrent server Interlink TCP/IP provider
EEWTCP27	Concurrent server for Openconnect TCP/IP stack
EEWTCP30	Child server task HCL Workload Automation
EEWTCP31	Child server task for Interlink TCP/IP stack
EEWTCP32	Child server task
EEWTCP84	SMF record exit for SMFEWTM
EEWTCP87	HCL Workload Automation interface
EEWTCP88	HCL Workload Automation interface post
EEWTCP89	CA-7 BTI
EEWTCP90	Issue command and wait for response
EEWTCP91	Issues TERROR to format messages and issues WTOS
EEWTCP92	Find substring within string
EEWTCP93	Issue CA-7 command and wait for response
EEWTCP94	STIMER exit to post ECB past in parm
EEWTCP95	Calls IKJEFF02 to extract buffer using EEWTCP99
EEWTCP96	ESTAE routine to issue failure message
EEWTCP97	Calls IKJEFF19 (DAIRFAIL/VSAMFAIL) to issue message
EEWTCP98	Calls IKJEFF02 to issue message from EEWTCP99
EEWTCP99	Message table
EEWTCPC7	Check CA-7 job
EEWTCPCA	Check application request handler
EEWTCPCF	Check file request handler
EEWTCPCJ	Check job request handler
EEWTCPCO	Check operation request handler
EEWTCPCV	Enumerate job
EEWTCPED	String encrypt/decrypt
EEWTCPEJ	Enumerate job request handler
EEWTCPFJ	Free job request handler
EEWTCPIA	Insert application
EEWTCPIE	String initialization
EEWTCPKJ	Kill job request handler
EEWTCPKO	Delete HCL Workload Automation application
EEWTCPL7	Launch CA-7 job request handler
EEWTCPLJ	Launch job request handler
EEWTCPLO	Insert HCL Workload Automation application
EEWTCPQ7	Query CA-7 job request handler
EEWTCPQJ	Query job request handler
EEWTCPQO	Query HCL Workload Automation application
EEWTCPQS	Query subsystem request handler
EEWTCPRC	Return code
EEWTCPSC	System abend
EEWTCPSE	String encryption/decryption
EEWTCPUC	User abend
EEWTCPWT	Wait for specified amount of time
EEWTCPXX	Invalid request handler

APAR PQ88345 add note below.

To assist in troubleshooting, be sure to obtain the JES log for the EEWSPACE and EEWSERVE started tasks. This will help in determining the context in which a message was issued. Depending on the job scheduling interface you use, additional helpful information may be obtained from other logs. For example, if you use CA-7, you should obtain the following:

The CA-7 log
The console log for the interval covering the test period
The job log of the job resulting in error (if this is the case)
The UNIX script file related to that job