Mainframe TDM Subsetting error. Receiving a -104 when the generated JCL from Subsetting places column value into column 72.

Document ID : KB000008685
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

We are getting a Mainframe TDM Subsetting error.  We are receiving a -104 when the generated JCL from Subsetting places a column value into column 72.   We have the value set to 72 in our template JCL:

...

[ACTION NAME]E.jcl

  </FILENAME>

  <LINEWIDTH>72</LINEWIDTH>

...

Environment:
DB2, z/OS, TDM, Subsetting
Cause:

This is not a Client issue, but an IBM limit: 

DSNTIAUL (and DSNTEP2/DSNTEP4/DSNTIAD) all only support SYSIN first 72 bytes. 
Beyond that the data must be split to multiple lines with no data in column 72. 
This is IBM limit. In CNTL datasets, "Normally" columns 72-80 are used for numbering. 

As it turns out, the Subsetting column names end exactly on column 72.  As a result, following the above requirements, there is an error being generated.

Resolution:

The resolution is to change the template from a value of 72 to 71.

...

[ACTION NAME]E.jcl

  </FILENAME>

  <LINEWIDTH>72</LINEWIDTH>

...

MUST be changed to 

...

[ACTION NAME]E.jcl

  </FILENAME>

  <LINEWIDTH>71</LINEWIDTH>

...