BMS Map - Copybook generation abend
Hi All,
I'm trying to setup a test environment with RTC 4.0 Enterprise Edition and RD&T. I'm using the sample application distributed by the jazz.net wiki (https://jazz.net/wiki/bin/view/Main/DependencyBuildScenario) with no additional changes.
Right now i'm just trying to get an Ant EE build to complete, but am having an issue with the copybook generation step of the BMS maps. The peculiar part is that RTC seems to abend before i'm able to get any helpful logging info. In other words, I get an OC1 as if a module was not found, but when I try to add a SYSUDUMP card to the translator, I get no output as the abend occurs before the SYSUDUMP. The same happens for SYSPRINT. Without any way to bring back this information, i'm at a loss for what could be going wrong.
In order to rule out my ASMA90 compiler, I wrote a sample BMS Map and generated COBOL via a simple JCL, which worked without problems.
Anybody have an idea what could be wrong or have seem a similar issue?
Thanks,
Scott
2 answers
Scott,
If you are using the sample project without modifications, temporary data sets are allocated to VIO. Would you try to change all string "VIO" to "SYSDA" in the setuprtcz.xml setup script and configure the environment with the modified script? We had a similar issue before (in our case it was S0C4 abend instead of S0C1) and it was resolved by replacing "VIO" to "SYSDA".
Tami (Masaaki) Takamiya
If you are using the sample project without modifications, temporary data sets are allocated to VIO. Would you try to change all string "VIO" to "SYSDA" in the setuprtcz.xml setup script and configure the environment with the modified script? We had a similar issue before (in our case it was S0C4 abend instead of S0C1) and it was resolved by replacing "VIO" to "SYSDA".
Tami (Masaaki) Takamiya
Comments
I have no good idea on what's going on...
In the build log, you can see the output of 'ulimit -a' command like:
* core file 8192b
* cpu time unlimited
* data size unlimited
* file size unlimited
* stack size unlimited
* file descriptors 64000
* address space unlimited
* memory above bar 17592186040320m
Is the address space of your build environment also set to 'unlimited'?
Tami (Masaaki) Takamiya
In the build log, you can see the output of 'ulimit -a' command like:
* core file 8192b
* cpu time unlimited
* data size unlimited
* file size unlimited
* stack size unlimited
* file descriptors 64000
* address space unlimited
* memory above bar 17592186040320m
Is the address space of your build environment also set to 'unlimited'?
Tami (Masaaki) Takamiya
Comments
Millard Ellingsworth
FORUM ADMINISTRATOR / JAZZ DEVELOPER Jan 23 '13, 5:44 p.m.Scott Pecnik
Jan 23 '13, 6:07 p.m.