Originally posted by: SystemAdmin

I am working with a typetree in my map that was imported from a cobol copybook. The map runs successfully but when I verify the output, the unused fields are not padding correctly. I do not see any property differences between the fields which pad correctly and those that don't. In some cases a field that should pad to 10 bytes long and has been mapped to NONE results in 5 byte padding in my output file. In a few other fields, I am seeing padding which exceeds the max field length specified for the element. In one such element, the length should be 9 bytes but the output file has 10 bytes. This is a fixed length file with no delimiters defined so the extra spaces aren't coming from a phantom delimiter.

Any help is appreciated.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: NancyR

It would be helpful to look at your type tree or at least a screen shot of the properties of the offending types.

Having fields whose padding exceeds the maximum size is sometimes caused by taking bytes out of a Filler field to create a new field. For example, if your Filler field is 200 bytes in the original copybook it should be padded to 200 bytes in the type tree when it's first imported. If a new field is added just before this filler at a later time, most people choose to add the field to the type tree and decrement the maximum size of the Filler rather than reimporting and risk losing any changes that were made. However, you must also edit the Pad to size or it will remain at its original value of 200 (in my example).
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

My tree is attached. I'm not sure my problem is what you've described. One of the fields that is adding in extra spaces is CLM-OUTSD-LAB-FACILTY-ZIP. One that is giving me 5 bytes rather than 10 is WOC-RENDERING-NPI-PFX.
#IBMSterlingTransformationExtender
#DataExchange
#IBM-Websphere-Transformation-Extender

Originally posted by: NancyR

The problem with CLM-OUTSD-LAB-FACILTY-ZIP is it's only padded in a fixed group and CLM_OUTSD_LAB_INDICATOR CLM Field isn't fixed. Ditton for WOC-RENDERING-NPI-PFX.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Oops, that WOC field doesn't pad at all but should be padding to 5 bytes, not 10.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Every field in the tree has padding applied in "Any context", but the problem with the padding only exists in certain fields.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: NancyR

Oops. My error.

Since this is output did you try running the debugger?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Hello! Not sure what version you are running but 6.7 has in the past put spaces in the Special Value property in the type tree for that field.

This in under Item Subclass then None then Special Value and you must put the cursor in the field then hit the End key to go to the end and if it is not at the first position then you know this is what happened. Then you would have to hit the Backspace key to remove those spaces from the field and analyze the tree.

Make sure the Required On Input right below that property is set to NO too.

Might want to check all your input and output fields and make sure they do not have this.

Have only found this in 6.7 and not 8.0 but it has happened plenty of times. Not sure if there is a type tree tool setting which makes this the default but some trees created here have had to be changed due to this.

Hope this helps.

Thanks!
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

That worked! It was a pain to change this setting in a couple hundred fields but it fixed both problems I was having. THANK YOU SO MUCH!
#DataExchange
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender

Originally posted by: TarunB

Not sure of exactly what you changed but you could have perhaps used the Propagate facility to filter the same change down through all of the fields.

This might have involved some temporary movement of fields to be under the same category, but it might have saved you having to update 200 fields individually :)
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

I wanted to mention that I am using version 8.1.0.3 so the issue Robert saw with version 6.7 still exists in the Copybook Importer.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange