I have a COBOL exe program which calls a COBOL dll which in turn calls a COBOL program using a dos interrupt 'x91 - the calling program uses an 'x91' to activate an EXE file as if it were typed in as an operating system command line entry. The security program which wraps my cobol code is a third party program which wraps around my program. The author has suggested that my program read environment variables to insure that the security has not been hacked. I have been unable to get my cobol to read the variables, so I thought that writing the program in C, the variables could be read. All the present program does is create a small sequential file, write one record to it and close the file - for security, I have the program wrapped by third party security software, and it generates the variables I want to verify to allow the progam to write the record weith the contents of the security check as passed or not passed. the calling program (a cobol dll) then tests for the presence of the file, reads the record and validates whether the code for security has been written into the file.
The COBOL program needs to be translated to C++ because the author of the security wrapping code says he can't interface with cobol executables.
- The present program is small
- All it does is create a small sequential flat text file, write one record to it, and then write the record and close the file.
- The program needs to check for the presence and value of certain "environment" variables being generated by a security program which wraps around the little program generating the file, and runs while the wrapped program is running.
For example, the variable "LICENSE" Returns the name of the current license used. thanks for any input.
The author of the security software has been unable to provide a small executable to check his variables, so I am looking to create one from scratch which will emulate the little cobol program I have been referring to (read the environment variables of the security program wrapping and securing my little program, create a file, write one record to it, the contents of which depend on the environment variable's values, and then close the file). In this way, the calling DLL will receive the file written by the small program executed by 'x91' call to the operating system (the one which needs to be coded in C++ instead of the present Cobol), verify its contents, and either allow the main program to procede or not. The main software consists of over 500 programs which I have ported from mainframe legacy code to PC. I used to use dongles but my clients hated them as they interferred with their printers...
the DOS call which activates the new little wrapped program will work with any executable program so it really is not an issue..