As of SBM 11.5, the default behavior for field mapping in post, copy, and create subtask transitions has changed. Prior to 11.5, when copying field values to another item, the system used default mappings for each field , but you could override those mappings by explicitly mapping fields . For example, when posting an item into the same primary table, all field values were copied to the new item and any manual field mappings that you made would override the default mapping.
When adding a new row of multi-value and multi-column attributes , the default values are not copied over as expected within the Desktop Client. These default values include $TODAYS_DATE and $USER_NAME.
Using DUP or XCOPY, when StarTool sees an LRECL=0, it assumes that the output dataset attributes are incomplete and then performs a non-zero merge of LRECL from the input data set to the output data set. StarTool does not look at the DISP (for example, DISP=SHR) specified for the dataset when performing this process.
If you want FDM to use it’s own internal copy routine and create a sequential dataset with attributes that match the input dataset, then specify ‘Use Record Selection==> YES’. Using the online panels, the specification for record selection follows the allocations for a NEW dataset on panel PDSM1PCC.
