z/OS Mainframe TPT RECFM=FB versus LRECL=VB - response (3) by rsilvers

What type of bug fixes have you impemented ? We are currently at TPT Version 13.10.00.04 on a Enterprise system used by hundereds of people ...it is not easy to upgrade to latest versionu unless for a very good reason
We are new to TPT and have just started replacing the old generation load/unload utilities. The way I understand this indicator bit....TPT creates 1 bit for each field that is nullable and then 8 fields/8 bits make a byte which is an indicator byte. This looks to be true because the jobs private log shows             
INDICATOR BYTES NEEDED: 8          
EXPECTED RECORD LENGTH: 383        
My schema has 64 coulmns and all are NULLable but none contain NULL values....
Did some experimenting and turned on INDICATORMODE='Y' with RECFM=FB and I'm assuming these are indicator bytes at front of file, like the manual states 
----+----1-
***********
.......2013
 
In HEX mode they are x'00' which is LOW-VALUES in mainframe world
.......2013
0000000FFFF
00000002013
The value I'm getting at end of record when INDICATORMODE='N' is same x'00'  
TUU    ........
EEE444400000000
344000000000000
And private log still shows
INDICATOR BYTES NEEDED: 8        
EXPECTED RECORD LENGTH: 383      
If you need the logs or a trace let me know and I can send.....