Maintaining Output Jobs

Workflow

• Manual resending of output files

  Output files can be resent in 'Output. Manage per Job' (MNS270) by selecting option 1='Send'.

  For Streamserve and storyteller service ID, you can also change the service ID on (MNS270/E) before resending the file.

  For IDM service ID (single interface and double interface), changing of service ID is not allowed. (MNS270/E) is disabled.

• Automatic resending of output files

  If, for some reason, the output cannot be sent, you can automatically resend output files by setting up the (MNS950) Auto job in 'Subsystem Job. Open' (MNS050). In each run, the (MNS950) job tries to resend each output file with status 'MSG' in (MNS270) for a maximum of three days.

  Message ID S_02012 in (MNS950) is used for processing Infor Document Management (IDM) connection failures (that is, IDM server is down or not responding). When using an IDM service ID (communication type 3 and 6), the automatic resending of output will only be triggered when the (MNS270) job status is MSG, and when the error message ID is S_02012. The number of retries or the time limit set for Streamserve is also applied to IDM, so that only records created in the last 24 hours are resent.

  For grouped output, when manually resending records in (MNS271), the (MNS270) status stays at MSG until all records in (MNS271) have been resent successfully. This means when (MNS950) runs, it will still resend the (MNS271) records that have been manually resent.

  For grouped and ungrouped outputs mixed in the same (MNS270) job, manually resending an ungrouped output first changes that message ID to S_01853. When (MNS950) runs, it will not be able to resend it because message ID is not S_02012.

• Manual deletion of output files

  You can delete output files manually in (MNS270). By selecting 'Delete', you remove the control record, the output file, and the related records and files.

• Delete obsolete files in batch

  You can delete obsolete output files in batch through 'Output Data. Delete' (MNS906). The delete function can be run on a regular basis if (MNS906) is defined in the M3 scheduler.