On 2016-01-05 12:35, Ed Jaffe wrote: > > I agree it would be nice to be able to insert a job step on the z/OS side to > transform a GOFF object into something consumable by z/VSE -- either object > deck or phase. > HLASM can generate either GOFF or traditional object format. You need GOFF only if you're using a feature not supported by traditional format, in which case transforming to traditional format sacrifices that feature.
But an exception should be made for ALIGN(16) in DSECTs. What does Dignus do translating GOFF with ALIGN(16) to traditional object. It should issue at least a warning. -- gil
