I am trying to find a clause by which i can get the name of executable
,is it possible to print COBOL executable name when executable is run
With Enterprise COBOL on z/OS, you might try looking at the prolog, either the entry name, found in PPA1 or the compilation unit name, found in PPA4 - more info about this on Knowledge Center.
Related
I am pretty new to Informix and I have a program that I am adding some functionality to.
It seems that the program has some existing issues with it though.
When I run make -f makefile.mk I get success and the .4ge gets generated and I am able to run it.
However I am trying to get the program to run within informix 4gl interactive debugger but I get the error: Invalid module name [main] specified.
Any assistance would be greatly appreciated. Unfortunately I am unable to share code as the program contains confidential information
The Informix-4GL Interactive Debugger (ID) is for debugging programs compiled with the Informix-4GL Rapid Development System (RDS). The object files created by RDS (fglpc) have the extension .4go (I4GL p-code object file) and the executables are conventionally given the extension .4gi (I4GL p-code interpretable file — run using fglgo or ID's fgldb).
By contrast, the plain Informix-4GL (c-code) system uses an I4GL compiler to generate first ESQL/C code and then C code, and a C compiler to create regular object files (.o) and to create its executables, which are conventionally given the extension .4ge (I4GL c-code executable).
The ID cannot debug c-code executables. It can only debug p-code interpretable files.
On the face of it, therefore, your problem is that you are using the wrong tool for the job. Either you need to compile with RDS and create an interpretable, or you need to use a C code debugger such as GDB. However, be warned that debugging I4GL code with GDB is mainly an exercise in frustration as the bulk of the code is a series of function calls to library functions — or is an incredibly tortuous sequence of goto statements if you're debugging inside an I4GL report function. It is machine-generated C code; it is not intended to be comprehensible to humans.
I'm very new to LaTeX and its distributions so this might be a very newbie question.
I was following this tutorial and I'm not being able to compile the document. The code so far is very simple i don't think there are any typos and also I did not find a similar question in the forum.
can someone point me in the right direction ?
I'm using windows XP and I've installed TexMaker 4.4.1 found here
The code I have so far is simply:
\documentclass[11pt]{article}
\begin{document}
This is my first LaTeX document.
\end{document}
the error I'm getting is:
Could not start the command. pdflatex -synctex=1
-interaction=nonstopmode %.tex
Cheers !
If you meet the error:
Error : could not start the command
while executing TexMakerX commands in Windows 7 x64, it is probably due to environment path of LaTex compiler.
The following steps may help you solve this error:
Make sure that you did install a LaTex compiler like MiKTeX. You know, TexMakerX is just an editor of latex input, not a compiler.
Locate the bin directory in the installation directory of the LaTex compiler.
Add the directory of bin like d:\Program Files (x86)\MiKTeX 2.9\miktex\bin to the environment paths of Windows.
Right click computer in start menu, choose properties.
Find the "Advanced system settings" in upper left corner.
Click the button "Environment Variables".
Find the row of variable path in the group of "System Variables" and add bin path like ;d:\Program Files (x86)\MiKTeX 2.9\miktex\bin to the tail.
Remember to add a semicolon to separate different path.
Then, try it again...
I found this question on another forum and it says that you should install MiKTex for windows too. Worked like a charm !
I came across a page which mentions that MiKTeX has two major bugs due to which users haven't been able to compile at all.
Use TeX Live compiler instead
Source
https://wiki.lyx.org/Windows/TeXLive
Most of the time errors occur due to space in the file names. while saving the Latex file one should always remember don't put spaces in between the file name.
I am new to COBOL programming.
I am making changes to a COBOL program which manipulates threads.I have introduced a file in the program to read a set of parameters and use it in the program. But whenever I compile the program I get the following warning:-
*1237-W
**Filehandling used with REENTRANT Directive
Now am I supposed to use the RENT option to compile this program? If so, then how should I compile using RENT option ie. the exact commands to be used.
Please help.
The error message number implies you are using Micro Focus COBOL, so depending on
the platform you can do:
Unix:
cob -C REENTRANT fred.cbl
Windows:
cobol fred.cbl REENTRANT;
cbllink fred.obj
or you can add the option to the actual source code itself eg:
$set REENTRANT
I've just started learning Lua, and I'm trying to get the native Lua interpreter to run a program that has been saved to a .txt file. I'm running Windows Vista with Lua 5.1.4.
Perhaps I'm missing something, but the only thing my book (Programming in Lua) says is that all you have to do to run your program is to call the interpreter with the name of the text file that contains your program. Then it gives this supposedly handy piece of code:
% lua filename.lua
Which I can't get to work in cmd or in the Lua interpreter. Further research I've done indicates that I might need to use a
dofile("filename.lua")
command, but I'm not sure how to do this. Specifically, what information do I need to put in the argument? Any help you can give is greatly appreciated.
You need to download a Win32 binary (see lua-5.2.1_Win32_bin.zip or lua-5.2.1_Win64_bin.zip here). Unzip this somewhere. How to run your script, in order of easiness and inverse order or common procedure:
Drag your script onto the Lua.exe using the Windows file Explorer.
a. Move your script to the same folder as Lua.exe
b. Shift right-click on that folder and select Open Command Window Here.
c. Type lua filename.lua and press Enter.
Add the directory containing Lua.exe to your system PATH, then do steps 2a and 2b on the folder containing your script.
Integrate Lua.exe with your editor in some way (how you do this depends on your editor).
We need to get data out of an older accounting system. We have received a dll that gives us access to the data we need. It includes a type library that we have imported.
If we run our test application from the same directory as the accounting system, everything works fine. If we try to run our application from a different directory, we get the following error:
Dynamically Bound RTS
Runtime DLL 'OOPS', version 3.1, entry point oops
not recorded in registry, not found or incompatible with requirements
of dynamically bound COBOL program. Dynamic binding of RTS requires:
Runtime DLL 'OOLSM', at least Version 3.1
Can anybody provide some helpful information on this?
Are we supposed to have some kind of cobol runtime in our directory? Or in the path? Or registered in the registry?
Thanks,
-Vegar
Updates:
Setting the system %path% to include the path to the accounting system seems to do the trick. Including it as a user variable did not have the same effect for some reason.
What Cobol are you using?
I had done this for year with Microfocus NetExpress 3.1, and all works just fine.
I write COBOL DLL to access COBOL data files, and also write Delphi DLL to add new features to old COBOL systens.
And yes, I use to set the runtime path, that is environment variable called COBDIR, there are others,but usually %PATH% and %COBDIR%is enough.
If you give more detais about what COBOL compiler are you using, and how is the dll interface that you are calling, will me ore easy to help you.
And maybe "Dependence Walker" can help you to identify what run time files are missing, if it is.
http://www.dependencywalker.com/
If it works from the accounting app's directory, but not a different one, the first thing I'd try is adding that directory to your path.
Unless it is already loaded into memory, Windows looks for DLL's that a program is requesting in every location listed in its PATH environment variable, and also in the directory the application is located within.