Good bye Cobol code? Long live short file path!!!
Recently I have come across some finance applications written in - Cobol.
The vendors will not like to mention directly (why? it is not a shame to write applications in Cobol as long as it works and lives well with other applications and the host operating system!). However, through prompt-up runtime error and installation runtime libraries they reveal themselves.
The real problem is lazy program practice: modern Cobol compilers have allowed more flexible locations for file path. Unfortunately this is not the case for our programs. There are mysterious printing failures. After long time troubleshooting, it comes back to 'printer path too long'!!!
What is happening to their project manager?
The vendors will not like to mention directly (why? it is not a shame to write applications in Cobol as long as it works and lives well with other applications and the host operating system!). However, through prompt-up runtime error and installation runtime libraries they reveal themselves.
The real problem is lazy program practice: modern Cobol compilers have allowed more flexible locations for file path. Unfortunately this is not the case for our programs. There are mysterious printing failures. After long time troubleshooting, it comes back to 'printer path too long'!!!
What is happening to their project manager?
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home