The Date Simulator started task program WARPMAIN receives messages IEFUTL02I and IEF170I every 30 minutes. Why?

book

Article ID: 127150

calendar_today

Updated On:

Products

CA Date Simulator

Issue/Introduction



The client just installed Date Simulator r 2.0 at the latest fix level TF1D336 and started the Date Simulator WARPMAIN started task. The WARPMAIN started task is required to be active on the LPAR in order to use Date Simulator.  The client notices the following Messages IEFUTL02I and IEF170I in the Date Simulator Started task every 30 minutes. What are these messages? 

12.06.36 STC08693 IEFUTL02I WAIT TIME ELAPSED FOR DATESIM - 30 MORE MINUTES GIVEN 
12.06.36 STC08693 IEF170I 1 DATESIM IEFUTL02I WAIT TIME ELAPSED FOR DATESIM - 30 MORE 

Environment

Z/OS
 

Resolution

It appears that an IBM SMF Exit has been configured on the TEST LPAR . This was most likely setup to detect looping programs. 

11.34.46 STC08693 WARP101I: DATE SIMULATOR V200 IS NOW ACTIVE 

12.06.36 STC08693 IEFUTL02I WAIT TIME ELAPSED FOR DATESIM - 30 MORE MINUTES GIVEN 
12.06.36 STC08693 IEF170I 1 DATESIM IEFUTL02I WAIT TIME ELAPSED FOR DATESIM 

The message IEFUTL02I starts with IEFUTL* 

z/OS MVS Installation Exits 

IEFUTL — Time Limit Exit 

IEFUTL receives control from the system when one of the following time limits expires: 

Job processor time limit (from the JOB statement) 

Step processor time limit (from the EXEC statement or the default from the job entry subsystem) 

Continuous wait time limit for the job (from the SMFPRMxx JWT parameter). "Continuous wait time" is defined as time spent waiting while the application program 

For additional information Please see link


***
***

The resolution was to add the TIME parameter to the JOBCARD       TIME=NOLIMIT

The TIME parameter on the JOB or EXEC statement specifies the maximum length of time a job or step is to use the processor. Two benefits of the TIME parameter are: 

The system prints the actual processor time used by the job or step in the messages in the job log. 

When a job or step exceeds the amount of time coded on the TIME parameter, the system abnormally terminates it or gives control to an installation exit routine established through System Management Facilities (SMF). 
Thus, the TIME value limits the processor time wasted by a looping program. 

By coding TIME=1440 or TIME=NOLIMIT, the TIME parameter can instead be used to give a job or step an unlimited amount of time. Specifically, the system allows a step to remain in a continuous wait state for an unlimited time, rather than the time limit established through SMF. However, if TIME=1440 is specified on the JOB statement, any TIME values on an EXEC statement and any default TIME values will be nullified. All steps within the job will have unlimited time, as with TIME=1440 or TIME=NOLIMIT.

For additional information Please see link