dfconv.exe

Hi,

in Server 5.1I have dfconv.lbr

in Cobol Server 2.3.1 have dfconv.exe

the same command line that work on server 5.1

"run.exe dfconv d:\tmp\flsetl\mnt\gluster\pocs3\prod\sw\prod\xx\conb\scripts\utilities\conf\flsetl.PRO d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl.SRT d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl-CRE.dat"

write the output file :

d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl-CRE.dat

d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl-CRE.idx

don't work in Cobol Server 2.3.1

"dfconv.exe d:\tmp\flsetl\mnt\gluster\pocs3\prod\sw\prod\xx\conb\scripts\utilities\conf\flsetl.PRO d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl.SRT d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.473816485-14728\flsetl-CRE.dat"

write the output file :

d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.4738

d:\tmp\flsetl\prod\dati\work\utilities\tmp\txt2dat\2016-06-27-17.10.32.idx

this limit why?


thanks

Parents
  • Hello mf_galberico:

    It should work the same, possibly depending on the contents of the file "flsetl.PRO".

    I recommend that you create a zip archive containing just the three files flsetl.PRO, flsetl.SRT, and flsetl-CRE.dat, then open a support incident to represent this problem through your account at supportline.microfocus.com, and attach the zip archive to the support incident.  Or attach each of the three files individually.  Then we could try the same experiment on machines at Micro Focus, comparing the behavior of dfconv between Server 5.1 with Server 2.3.1.

Reply
  • Hello mf_galberico:

    It should work the same, possibly depending on the contents of the file "flsetl.PRO".

    I recommend that you create a zip archive containing just the three files flsetl.PRO, flsetl.SRT, and flsetl-CRE.dat, then open a support incident to represent this problem through your account at supportline.microfocus.com, and attach the zip archive to the support incident.  Or attach each of the three files individually.  Then we could try the same experiment on machines at Micro Focus, comparing the behavior of dfconv between Server 5.1 with Server 2.3.1.

Children
No Data