The AFC job is expected to react to incoming spooled files. If that is not the case, then you should consider the check list below:
1.Is the spooled file in status Ready (*RDY)? If the spooled file has arrived on the output queue with status Held (*HLD), then the AFC job is unable to see the new spooled file. To trigger the AFC job, the spooled file should either arrive on the output queue in status *RDY, or you should release the spooled file while placed on the monitored output queue.
2.Is the Auto_Form subsystem running? You can verify that via option 12 on the Auto Forms Control Main menu. If not, then it should be started.
3.Is the monitor job for this specific output queue started? You should be able to see the job in the Auto_form subsystem e.g. via option 12 on the Auto Forms Control Main menu.If not, then you can start the specific job manually.
4.Is there a data queue in the same library as the monitored output queue with the same name as the output queue? If yes: You can verify if the data queue is connected to the output queue with the command: WRKOUTQD, which should look like below. If the data queue is missing, then you can create it by selecting option 2=Change for the monitored output queue on the AFC output queue setup and press Enter twice. After this you will need to (hold and) release any spooled file, that the AFC job should react to.
Work with Output Queue Description
Queue: PRT01_IN Library: QUSRSYS
Status: Writer active . . . . . . . . . . . : N Writer name(s) if active . . . . . . : Output queue held . . . . . . . . . : N Maximum spooled file size: Number of pages . . . . . . . . . . : *NONE Starting time . . . . . . . . . . . : Ending time . . . . . . . . . . . . : Writers to autostart . . . . . . . . . : *NONE Display any file . . . . . . . . . . . : *NO Job separators . . . . . . . . . . . . : 0 Operator controlled . . . . . . . . . : *YES Order of files on queue . . . . . . . : *FIFO Data queue . . . . . . . . . . . . . . : PRT01_IN Library . . . . . . . . . . . . . . : QUSRSYS
|
5. It can also be, that the used data queue is damaged. You can see that with the command DSPOBJD. The section below describes how this can be fixed.
