No output - what to do if the task is not in the system
If
you have obtained no output and CEMT INQ TASK shows the task is not in the
system, one of two things could have happened:
- Your transaction never started.
- Your transaction ran, but produced no output.
Note: If you’re not getting output on a printer, the reason could be that you are not setting on the START PRINTER bit in the write control character. You need to set this bit to get printed output if you have specified the STRFIELD option on a CONVERSE or SEND command, which means that the data area specified in the FROM option contains structured fields. Your application must set up the contents of the structured fields.
Your task might have been initiated by direct request from a terminal, or by automatic task initiation (ATI). Most of the techniques apply to both sorts of task, but there are some extra things to investigate for ATI tasks. Carry out the tests which apply to all tasks first, then go on to the tests for ATI tasks if you need to.