If data from multiple systems is written using the sequential output file (//ATHDATA) then each system’s records will be written end-to-end. This data includes the target number, and Control Center can determine to which system it belongs. For Control Center to correctly process this data, the file name must be set to a special case of :
YYYYMMDDhhmmss_aszsMULTIZOS.<number>
Here the target number is replaced with a fixed string of MULTIZOS to indicate to Control Center that target numbers must be taken from the data instead of the file name.
This file must be placed in the location defined to System Manager
Important note! Note that the file name does not contain a target number. A file conforming to this style of name will be picked up by any collection thread set to scan a given location. If you use this form of file naming, and have multiple MULTIZOS files being copied to a single location, set only one of the Targets to collect files in System Manager, and make sure the others all have the Connection Enabled tick box set off.
Failure to do this will mean that Control Center collection threads will “fight” over MULTIZOS files, causing possible failure to store data in your database, accompanied by error messages in the event log.
Alternatively, if you ensure that MULTIZOS files are put in unique locations, you can then continue to have Control Center collect data from each one.
The ACQPUSH utility can help to automate the copying of MULTIZOS data from the mainframe to the Control Center system, as detailed below.