WIP: First Cut - this doesn't work yet - a work-in-progress.

[mbeckerle]

Doesn't work in Daffodil for lack of "V" textNumberPattern feature.

Doesn't work in IBM DFDL for lack of binaryCalendarRep="packed" support.
Also needs dfdl:calendarTimeZone="UTC" because "" is not accepted - this will require changing the test logical data to have "+00:00" on the dates.

[mbeckerle]

Ok, to be clear, IBM DFDL has lots of working Cobol capability. What isn't working is my little example here yet. Presumably it can be made to work with a workaround to the issues blocking me.

[mbeckerle]

Not yet ready for prime time.

[mbeckerle]

This workaround isn't working-around yet. There may be a better way to do this.

[smhdfdl]

@mbeckerle When IBM creates DFDL schema for COBOL, we auto-generate them from the COBOL copybook or program. There is no concept of a date/time data type in COBOL, and that kind of data normally would be represented as string or zoned decimal. We have never needed to generate binaryCalendarRep="packed".

[smhdfdl]

@mbeckerle Suggested default properties for COBOL ... as there is no date/time concept in COBOL, there is nothing declared for date/time.

<dfdl:format 
  representation="text" 
  escapeSchemeRef="" 
  ignoreCase="yes" 
  initiatedContent="no"
  alignment="1" alignmentUnits="bytes" 
  textStandardBase="10"  textNumberCheckPolicy="lax"  
  textStandardZeroRep="0" textStandardExponentCharacter="E"
  textStandardDecimalSeparator="." textStandardGroupingSeparator="," 
  textNumberRoundingMode="roundUp"  textNumberRounding="pattern"
  textNumberJustification="right" textPadKind="padChar" textTrimKind="padChar" 
  sequenceKind="ordered"  floating="no"
  textOutputMinLength="0"
  truncateSpecifiedLengthString="no"
  nilValueDelimiterPolicy="both" emptyValueDelimiterPolicy="none"
  documentFinalTerminatorCanBeMissing="no"
  useNilForDefault="yes" 
  choiceLengthKind="explicit" 
  fillByte="%#r00;"
  binaryNumberCheckPolicy="lax" 
  binaryBooleanTrueRep="1" binaryBooleanFalseRep="0"
  textBooleanTrueRep="true" textBooleanFalseRep="false" 
  textBooleanJustification="left" textBooleanPadCharacter="%SP;" 
  lengthKind="explicit" lengthUnits="bytes" 
  binaryNumberRep="binary"
  binaryPackedSignCodes="C D F C"
  outputNewLine="%CR;%LF;" textBidi="no" 
  initiator="" terminator="" 
  separator=""  separatorPolicy="required" separatorPosition="infix" 
  leadingSkip="0" trailingSkip="0" 
/>

[smhdfdl]

@mbeckerle Consider declaring simple types for all the COBOL PIC types. You can carry some properties on the simple types to avoid duplication. It also makes sense to a someone familiar with COBOL. Example:

	<xsd:simpleType name="PIC9-Comp3__short" dfdl:representation="binary"
		dfdl:binaryNumberRep="packed">
		<xsd:restriction base="xsd:unsignedShort">
			<xsd:minInclusive value="0" />
			<xsd:maxInclusive value="9999" />
		</xsd:restriction>
	</xsd:simpleType>

I can see if IBM can donate the full list of simple types.

[mbeckerle]

This got closed by accident. Should be reopened.