As SYMBOLIC-FILE and TARGET-IMAGE is not a matter of the pyhsical representation of calibration data, it is not handled in the proposale here. It appears to be an M:N relationship betweenn calibration data, target image and the symbolic file. In particular one physical set of data can be loaded in multiple systems if the calibration items are available. Also, one physical set of data may result in multiple target images according to the various possible symbolic files.
The following options would apply .
 
Derive the filename from <SW-CS-PROGRAM-IDENTIFIER>
 
Keep this information within <PRIVATE-CODES> within <ADMIN-DATA> (this is currently removed in the proposal here)
 
Keep this information within <SPECIAL-DATA> (this is currently removed in the proposal here).
 
Keep this information in a separate file (e.g. a Catalog using MSRCC.DTD).