Re: LE C growing heap issue

>classic fragmentation ... e.g. set to KEEP and increment size is too >small. Check your CEE_RUNOPTS or there could be other LE config/exits >involved. Suggest you set disp=FREE and work out increment size. > HEAP(initial, increment, location, disp, init24, incr24) > >On Fri, Jan 5, 202

Re: LE C growing heap issue

I could understand fragmentation being any issue if we did not return all the memory, but during each iteration we return all the application allocated memory, so how can memory become fragmented? -- For IBM-MAIN subscribe / sig

LE C growing heap issue

We are in a bit of a quandary here with some memory issues surrounding our application. This is a multitasking LE C application running in 31 bit mode that utilizes the IBM JSON and EZNOSQL Services. Some of the attributes are: • z/OS V2.5 Operation System • POSIX(OFF) - all tasks/s

Re: External Functions in C on z/OS

First of all thanks to Colin for sending me the headers. Before I went down the path of generating them myself, I want to see what other had experienced trying to do this. I can't use Metal C, as the routines I want to call out of the functions are not supported under Metal C. FWIW, I was lo

External Functions in C on z/OS

I've written quite a few callable external functions for Rexx over the years. On z/OS I've always used assembler as we needed to access system services for a variety of tasks. I've written them in C for other platforms (OS/2 & Windows) over the years. I need to write some on z/OS, but I want to

Re: Building AMODE 31 Assembler DLL

Thanks for the that pointer. I had not gotten to that manual as yet. But for a follow on question. As these are routines called from C, I've been using EDCPRLG as the entry code. Can I switch those out for CEEENTRY, as EDCPRLG does not have the EXPORT keyword. Taking a quick look at the CEEENTRY

Building AMODE 31 Assembler DLL

I've found a bunch of information on creating AMODE 64 Assembler DLLs, but having much luck in finding any information about creating AMODE31 Assembler DLLs. I've got a bunch of LE enabled assembler helper routines that I call from C, I want to package these all as a DLL so that I can share th

Re: C DLL abend CEE3350S

For a bit more information. If I don't include any of my Assembler routines in the DLL then the binder sets the CEESTART as the entry point. When I do include any of the Assembler routines, which use EDCPRLG as its entry code, then the one that ends of first in the sort order of names becomes th

Re: C DLL abend CEE3350S

I've already built another DLL successfully, albeit with just 1 module. And we are doing all this on the z/OS side and not the USS side so those commands are not available for use. -- For IBM-MAIN subscribe / signoff / archive a

Re: C DLL abend CEE3350S

These are the ones that are explicitly set. LANGLVL(EXTC1X) LIST ILP32 DEBUG(LEVEL(9)) AGGREGATE(OFFSETHEX) NOXPLINK DLL

Re: C DLL abend CEE3350S

I know, but the CEESTART CSECT is included in the program object. On another DLL, which is just 1 module with multiple functions, the CEESTART CSECT is listed in the load map as such. 0 CEESTART*

C DLL abend CEE3350S

I've a LE C DLL I've built that contains a several modules. It has both C and a LE callable Assembler routines. When I first bound the moudle, it did not set CEESTART as the entry point, so I added an ENTRY CEESTART to the binder input deck. This results in a load module that shows the following

Re: Built-In function unrecognized

Nope, thats not it. ARCH is set to 7 for both. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Built-In function unrecognized

I've got a set of XL C compiles where one is giving me a CCN3690 message and the other is not. I've scoured over the compiler options and both are getting fed the same ones. But the compile out of one environment (Dev) is giving the message, but the one out of the other (integration) does not. T

Re: Usage of strcasecmp gives implicit function warning even with

The #define of _POSIX_SOURCE fixed it. Darn documentation! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: z/OSMF

PLUGH! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Usage of strcasecmp gives implicit function warning even with

I'm a bit perplexed here. I'm using XL C and the strcasecmp function. I've included and added the #define for _XOPEN_SOURCE_EXTENDED as documented in the library reference, as shown below. But I still get a warning message for it. #define _XOPEN_SOURCE_EXTENDED 1 #include CCN4421 ... I

Re: regex always returns 1

array of at least nmatch elements. I thought that regexec would just return success/failure on the search. Apparently, I totally misunderstood the documentation, which is not uncommon :-> Thanks a bunch Eric Erickson -- For

regex always returns 1

I'm having an issue with trying to use a regular expression to validate an z/OS Dataset Name Qualifier. I traverse the DSN using strtok to extract a pointer to each qualifier. I built a regular expression that works using a web tool to identify any invalid characters. The string I build using th

Trace XL C Preprocessor input

Using XL C on z/OS V2R5. I've got a set of #ifdefs in a header file that are not giving me the results I expect. I know on other compilers I've used in the past that there were options to output all input statements showing the #ifdefs and how the logic was processed. I need the same thing for t

Re: LCCAWTIM on multiple CP System

Duh, I knew it was something simple. Of course I got milliseconds confused with microseconds. Now I feel slightly foolish. :-; Thanks Eric Erickson -- For IBM-MAIN subscribe / signoff / archive access instructions, send

LCCAWTIM on multiple CP System

I'm working on some code that tries to detect a loop in a subtask by examining the LCCAWTIM value for each CPU. My detector task runs in an STC that wakes up every .5 seconds and trolls through the LCCA Vector calculating deltas of wait time between iterations. The routine that retrieves the L