01-23-2009
Thanks
Althought there has been a 'technology upgrade' patch to the dev box I feel its something related to 32/64 bit mode. Whether this is OS patch related is proving difficult to determine.
The compile of the COBOL program isnt striaghtforward becuase I have to compile under 64 bit, then move the excutable & bind files over to the usserid running in 32 bit mode.
Looking at the dump the seg fault core dump the line
Segmentation fault in _iwzEnvNameInit
points to the goback command at the end of the program (see
IBM - SIGSEGV _iwzEnvNameInit)
But like I said this prgram hasn't changed.
10 More Discussions You Might Find Interesting
1. Programming
Okay, so here is some code that when compiled on Fedora Core 6 works great, but when I compile and run it on OpenSuse 10 it gives back a seg fault when trying to join the 2nd thead.
#include <pthread.h>
#include <stdio.h>
int print_message_function( void *ptr );
int x = 1;
main()
{
... (1 Reply)
Discussion started by: chrisdrobison
1 Replies
2. HP-UX
Hello everyone,
Today we are attempting to port some legacy C code to a 64 HP-UX machine at my company and there is kind of a strange error we ran into.
there is a small function they have defined called zgetenv that
accepts a char* and basically just does some null checking and returns ... (0 Replies)
Discussion started by: khadesh
0 Replies
3. Programming
Hi Forum,
i have such a question.
I have a cobol program which is calling a C program and in that C program
i get a core dump:(. I want to investigate what is the issue using WDB debuger, but a dont see the code from COBOL program in the debuger, when i run the debugger with the exe!!!
... (2 Replies)
Discussion started by: vovan
2 Replies
4. Programming
can i run .crn programme in express cobol which support to .gnt programme .... Plz tell me solution (2 Replies)
Discussion started by: bibi
2 Replies
5. Programming
Hi,
First of all forgive me if Xlib related problems does not go under this thread.
In my main program, im using Xlib`s XImage type object which contains a regularly updating bitmap, and maps the XImage to a Xwindow using XPutImage.
( XCreateImage is used to create the XImage. )
The... (0 Replies)
Discussion started by: wolwy_pete
0 Replies
6. Shell Programming and Scripting
Is there a way you can return a value from a script that is called from a rm cobol program...
01 WS-COMD-LINE-PGM X(39) value sh ./getUserId.sh 12345"
01 WS-RETURN-SYS-CODE PIC 9(8).
CALL "SYSTEM" USING WS-COMD-LINE-PGM
GIVING WS-RETURN-SYS-CODE.
... (1 Reply)
Discussion started by: pavanmp
1 Replies
7. Programming
Hi ,
We are migrating our database from DB2 z/os to DB2 UDB on UNIX.
and cobol on mainframes to AIX cobol on UNIX.
We have some cobol Db2 programs that are accessing different Databases
how do we code such type of programs in AIX cobol.
Do we need to Establish connection for accessing... (0 Replies)
Discussion started by: nal.satish
0 Replies
8. UNIX for Advanced & Expert Users
Hi Guys
Am new in UNIX environment I was asked by my boss to write a program that transfer files from the AIX server to the Wintel Server. I have written the program in C# windows which does almost the same thing. So how to run the C# program in UNIX? (1 Reply)
Discussion started by: michmsk
1 Replies
9. AIX
hi folks,
I am a new to Aix, i worked as sys admin so no idea about software probs, my software team requires Debugging tool for cobol in AIX machine.
can someone tell me the tool and also the installation procedure for the same
Please drag me out from this soon :confused: (1 Reply)
Discussion started by: atulgkwd
1 Replies
10. Shell Programming and Scripting
Hi All,
I have a file which sets all the variables on unix , based on the hostname. Currently these variables are hardcoded in the cobol programs.I was wondering if unix variables can be used in Cobol programs ?
Example :
I have a variable $SHTEMP which is set based on the following :
Prod... (2 Replies)
Discussion started by: nua7
2 Replies
LEARN ABOUT ULTRIX
savecore
savecore(8) System Manager's Manual savecore(8)
Name
savecore - save a core dump of the operating system
Syntax
/etc/savecore [ options ] dirname [ system ] [ corename ]
Description
The command is meant to be called near the end of the file. The command saves the core dump of the system (assuming one was made) and
writes a reboot message in the shutdown log.
The command checks the core dump to be certain it corresponds with the current running ULTRIX. If it does, it saves the core image in the
file dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n. The trailing .n in the pathnames is replaced by a number which
increments each time is run in that directory.
After saving the core and namelist images, will save the error logger buffer into a predetermined file. The error logger buffer contains
information about why the crash occurred. After completes, the daemon will extract the error logger file and translate its contents into a
form familiar to the program.
Before writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the filesystem that
contains dirname than the number obtained from the file, a core dump is not done. If the file does not exist, savecore always writes out
the core file (assuming that a core dump was taken).
The command also writes a reboot message in the shut down log. If the system crashed as a result of a panic, also records the panic string
in the shut down log.
For partial crash dumps, creates a sparse core image file in dirname/vmcore.n. If this sparse core image file is copied or moved to
another location, the file expands to its true size which can take too much file system space. Hence, to copy or move sparse core image
files, you must use the command. The command has a conversion option to create sparse output files.
Options
-c Clears the core dump. This option is useful when the core dump is corrupted in a way that will not allow to save it safely. Use the
option with caution, because once it clears the core dump, the core dump cannot be retrieved.
-d dumpdev dumplo
Specifies the dump device and the dump offset when running on a system image other than the currently running system image. The pro-
gram assumes that the running system image is and it reads the dump device and dump device offset are different in the system image
that crashed, the option provides the correct dump device and dump device offset.
-e Saves only the error logger buffer into a file. If used, core or namelist images are not saved.
-f corename
Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device. This option
is used only for diskless workstations.
If the core dump was from a system other than /vmunix, the name of that system must be supplied as system. The program assumes that the
running image is
After successful completion, the core dump is cleared. Also, a message is written in the file which tells whether the dump succeeded or
failed.
Files
Shut down log
Current running ULTRIX system
See Also
dd(1), uerf(8)
savecore(8)